projects: show ancestor path

[valentijnscholten]

Description

When searching for projects/components/vulnerabilities there's no visual indication of where in the Project Hierarchy a project is shown.

Addressed Issue

(partly) fixes #1353, #1362

Additional Details

In v4 we need to do perform some additional java code to get the "ancestor path" populated. But in v5 this will be easier due to the materialized view being used there. Happy to forward port the feature to v5.

I haven't created tests yet as I first would like to get confirmation this is something that can be added to v4. I know v5 is around the corner. At the same it might take some time before v5 is released as GA and everybody has moved over. This PR fixes a real need in v4.

API companion PR: #5827

Considerations

Having the full hierarchy view when displaying ony a subset/searchresult of projects is non-trivial to implement if we take features such as paging into account. Maybe for v5 someone has a better proposal, for now an additional column seems helpful in v4.

Disclaimer

I used AI for the Vue stuff.

Checklist

• I have read and understand the contributing guidelines
• This PR fixes a defect, and I have provided tests to verify that the fix is effective
• This PR implements an enhancement, and I have provided tests to verify that it works as intended
• This PR introduces changes to the database model, and I have added corresponding update logic
• This PR introduces new or alters existing behavior, and I have updated the documentation accordingly

[valentijnscholten]

@nscuro I have now refactored both PRs to show the ancestor path as tooltip instead of column. Not perfect, but better than nothing and maybe good to be accepted. I've also refactored the api reponse to just return the chain of parents in the parent block instead of a new ancestor path element.

Global Policy Audit doesn't have the full parent chain as that endpoint returned detached JDO Object which only have the direct parent. If we all like the tooltip approach and/or the parent chain response format I could look at refactoring this endpoint to use value objects instead of detached objects.

Plot twist: Should we just render the tooltip on the fly using an API call for that view (or all views)?

[owasp-dt-bot]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.