## TL;DR Add OWASP Top 10 2025 as a supported identifier standard in the vulnerability filtering pipeline by introducing the necessary constants, GraphQL types, and Elasticsearch filter support. ## Acceptance Criteria * [ ] OWASP Top 10 2025 category constants are defined in `Enums::Vulnerability::OWASP_TOP_10_BY_YEAR` * [ ]  A GraphQL enum type `VulnerabilityOwasp2025Top10` is available for API consumers * [ ]  `owaspTopTen2025` argument is available on the vulnerabilities and vulnerability severities count resolvers * [ ]  Filtering by `owaspTopTen2025` requires advanced vulnerability management and is not supported on Instance Security Dashboard * [ ]  Passing `NONE` alongside other OWASP 2025 values raises a validation error * [ ]  The Elasticsearch filter pipeline applies the OWASP 2025 filter correctly against `identifier_names` * [ ]  Specs cover the new enum type, resolver arguments, filter validation, and ES filter behavior ## Implementation Details * Add `'2025'` entry to `OWASP_TOP_10_BY_YEAR` in `app/models/concerns/enums/vulnerability.rb` with integer values 21-30 * Create `ee/app/graphql/types/vulnerabilities/owasp2025_top10_enum.rb` * Add `owasp_top_ten_2025` argument to `ee/app/graphql/resolvers/vulnerabilities_resolver.rb` and `vulnerability_severities_count_resolver.rb` * Add `owasp_top_10_2025` to `ADVANCED_FILTERS` and validation in `ee/app/graphql/resolvers/vulnerability_filterable.rb` * Add `"2025"` regex to `OWASP_REGEX_CONSTANTS_BY_YEAR` and `by_owasp_top_10_2025` method in `ee/lib/search/elastic/vulnerability_filters.rb` * Add `:by_owasp_top_10_2025` to `QUERY_COMPONENTS` in `ee/lib/search/elastic/vulnerability_query_builder.rb` * Add `owasp_top_10_2025` param mapping in `ee/lib/search/advanced_finders/security/vulnerability/base_finder.rb` ## Testing Approach - [ ] Unit tests - [ ] Integration tests - [ ] Manual validation steps ## Estimate