Feature: Support recursive retrieval of Dependency-Track findings

[rezdel]

Currently, the Dependency-Track integration only retrieves findings (violations/vulnerabilities) from the selected project itself.

When users organize projects hierarchically in Dependency-Track (e.g. Environment → Service → Application), selecting a parent project does not return findings from its child projects. This makes it impossible to create environment-level metrics and dashboards in Quality Time.

Use case
Organizations often use Dependency-Track project hierarchies to group applications by environment (e.g. DEV, TEST, ACC, PROD).

Users expect a metric configured on a parent project to include findings from all underlying child projects.

RC
├── Service A
├── Service B
└── Service C

Selecting RC should return findings from Service A, B and C.

Current behavior

• Only findings directly attached to the selected project are retrieved.
• Child project findings are ignored.

Expected behavior

• Findings from all descendant projects are included.
• The aggregation should be performed recursively through the project hierarchy.

Benefits

• Environment-wide reporting.
• Reduced configuration effort.
• Better alignment with Dependency-Track project structures.

Acceptance criteria

• Parent projects include findings from all descendants.
• Recursive traversal supports multiple hierarchy levels.
• Existing configurations remain backward compatible.