Remove maximum range limit in VulnerabilitiesPerSeverityResolver to allow querying without date constraints
Problem
The VulnerabilitiesPerSeverityResolver has a maximum range set to 365 days, which is causing issues with vulnerability count queries. This limitation prevents users from querying vulnerability data beyond the 365-day window, leading to discrepancies in vulnerability counts displayed in the Security Dashboard.
This issue is related to RFH: https://gitlab.com/gitlab-com/request-for-help/-/issues/3781, where customers experienced dramatic drops in vulnerability counts after the Security Dashboard UI update.
Proposed Solution
Remove the maximum range constraint from VulnerabilitiesPerSeverityResolver and allow users to not set the start and end date parameters. When dates are not provided, the finder should query without any date range restrictions, returning all vulnerabilities regardless of when they were detected.
Expected Outcome
- Users can query vulnerability data without being limited to a 365-day window
- Vulnerability counts will be consistent across different time ranges
- The Security Dashboard will display accurate vulnerability counts that match the actual state of the codebase