feature: new endpoint for crossunit team

[owens-hub-git]

Description

New endpoint for cross-unit dashboard team to fetch all projects along with their respective tasks

Fixes # (issue)

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Used swagger to test the endpoint implemented and provides the correct response

• Test A
• Test B

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation if appropriate
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• I have created or extended unit tests to address my new additions
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[cillynder]

Endpoint seems to work well, however, it might be best to have this as a query parameter instead (at /projects).

Additionally, it would be ideal to reuse the existing entities (ProjectEntity, TaskEntity, and TaskDefinitionEntity). This would greatly simplify the frontend implementation by allowing us to reuse the same models and also keeps the backend clean.

Could you please setup the endpoint such that it exposes the existing tasks of the project entity, and also a task_definitions with all the task defs, depending on a query parameter?