FE: Update scan result vulnerability states criteria to display automatically

Why are we doing this work

• see Policy Editor Rule Mode UX enhancements (&11079) for details

Implementation plan

• frontend update filters to not use null and [], but instead to get the information from the yaml
• frontend remove vulnerabilities_states: [] from default yaml
• frontend display vulnerabilities_states criteria UI by default with status New and All vulnerability states (yaml would be vulnerability_states: [new_dismissed, new_needs_triage]) selected in security_scan_rule_builder
• frontend when a user selects New and All vulnerability states, the vulnerabilities_states key is removed from the yaml if it is the only status in security_scan_rule_builder

Verification steps

1. Navigate to scan result policy editor rule mode
2. Verify that vulnerabilities_states criteria UI shows with New and All vulnerabilities states selected in rule mode and the vulnerabilities_states key is present in the yaml
3. User selects specific state
4. Verify that vulnerabilities_states key appears in yaml with selected values in an array
5. User selects All vulnerability states
6. Verify that vulnerabilities_states key in yaml is set to []
7. User adds another status with values
8. Verify that vulnerabilities_states key appears in yaml with selected values in an array