refactor: Remove the overlap between a Complexity Report and Feature List Report

[seantiz]

The purpose of Feature Report is unclear. Is it a bill of materials? We have to clean this up.

[seantiz]

Complexity Report

• Code metrics
• Listing all function calls
• Estimated time (which ideally would decay as soon as the job begins)
• Work breakdown structure
• Implementation details (would a mature codebase benefit for better spread of responsibilities?)

Feature Report

• Architectural relationships
• Dependencies between components
• Interface contracts

The Complexity Report becomes a tool for project planning and asking "Is this worth the effort for us?"

The Feature Report becomes a design document tool.

[seantiz]

I think we completely eliminated overlap with 8a2a9b9

But I'm keeping this open for now as there's a lot of room for testing and optimisation when it comes to layer classification of C++ codebases

A more typical (even if arbitrary) distribution in a C++ system might look closer to:

• Core: 15-20%
• Interface: 20-25%
• Derived: 40-45%
• Utility: 5-10%