Introduce "collection" projects for better usage of hierarchical view #2041

[rkg-mm]

Description

This change introduces UI logic for "collection projects". Those are basically projects used as parent for other projects that shall not hold any own component or vulnerability data, but instead get calculated from child projects using different configurable aggregation logics.

• Project Details/create dialog allow selection of different collection logics (all direct children, direct children with custom tag, only highest SemVer child)
• Collection projects are visually marked in project list and get shown aggregated metrics. The used calculation logic is displayed on mouseover of calc icon
• Project page hides all unrelevant tabs, instead shows a new tab with all child projects. For this the project list is made reusable
• Additionally:
  ** Fixes some routing bugs

Required Backend PR: DependencyTrack/dependency-track#3258

Addressed Issue

DependencyTrack/dependency-track#2041
DependencyTrack/dependency-track#657
DependencyTrack/dependency-track#2410
#641 (routing Bug)

Additional Details

Checklist

• I have read and understand the contributing guidelines
• This PR introduces new or alters existing behavior, and I have updated the documentation accordingly

[123Haynes]

This is a feature I would love to see in dependencytrack. Would certainly make it easier to structure projects and see the issues at a glance.

@nscuro Is there anything left todo to be able to merge this pr and the corresponding backend pr?
It looks like this feature was finished month ago, but is just kinda floating around without getting merged.
Is there anything people can help with to get this over the finish line?

[rkg-mm]

Warning: I fixed a lot of conflicts and did not have time to test it. Will try to find time tomorrow to test it. Furthermore I threw out my bugfix for the double loading logic as @nscuro already did another fix for this

[rkg-mm]

[deleted - belonged to backend]

[rkg-mm]

Should be good to go :)
[closed by accident.. wrong button - reopened :D ]

[rkg-mm]

@nscuro do I need to do something for the failed checks? the i18n issues don't seem to be from my changes, and the other Linter I don't see where I can find the actual output of whats wrong, only the files it complains about.

[nscuro]

Just gave this a spin. I didn't test super extensively yet but wanted to note it down before I forget.

I created a collection project and uploaded about 50 or so BOMs to it. I selected collection logic Direct children with tag.

Looking at the list of projects, either in the Projects or Project -> Collection projects view, show no indication which project counts towards the metrics. I am seeing the metrics of the collection project, but I have no idea how they came to be.

Looking at projects in the list doesn't give a hint either. This might be more of a problem once you have more than 10 projects, so they don't all fit on a single page anymore.

I think some kind of visual cue is needed to make it clear which projects are counted towards the collection's metrics.

With only the Aggregate direct children option, this would not be a problem. However once we limit aggregation to a subset, we need to make it visible what subset that is, somehow.