feat: [five-c] Create extended policy rules set #411

[tdruez]

Issues

• Issues: five-c: Create extended policy rules set #411

Changes

• Three new vulnerability rules covering vulnerability detection, unresolved triage, and stale high-risk vulnerabilities
• Configurable parameters per rule (minimum risk score, maximum days unaddressed) resolved from the per-dataspace configuration
• detected_date field added to package-vulnerability links to track when a vulnerability was first recorded
• Inventory filter by policy rule to show only packages that triggered a specific rule, shared across the product relation filtersets
• Compliance tab badge updated to "triggered" with color reflecting the highest violation severity (red for error, yellow for warning)
• Violation table ordering follows the rule registry order rather than alphabetical
• Violation count on the dashboard now excludes obsolete rule types no longer present in the registry

New extended policy rules

Rule	Severity	Description
Vulnerability Detected	Error	Packages with at least one known vulnerability, with an optional minimum risk score
Vulnerability Unresolved	Warning	Packages with known vulnerabilities and no completed vulnerability analysis
Vulnerability Stale	Error	Packages with high-risk vulnerabilities unaddressed beyond a configured number of days

All rules count the number of affected packages in a product. A rule triggers when that count exceeds the configured threshold (default: 0, meaning any match triggers).

Screens