Display a group by dropdown

What does this MR do and why?

This MR does two things:

• Introduce :vulnerability_report_grouping feature flag
• Display a listbox on the project vulnerability report when the feature flag is enabled

Screenshots or screen recordings

Before	After

How to set up and validate locally

1. Enable :vulnerability_report_grouping feature flag: echo "Feature.enable(:vulnerability_report_grouping)" | rails c
2. Fork https://gitlab.com/gitlab-examples/security/security-reports
3. Run a pipeline against the default branch
4. Visit Secure > Vulnerability Report
5. See the group by button

It currently does nothing other than setting the state. Upcoming work will introduce more functionality.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.

Related to #420055 (closed)

.gitlab/ci/rules.gitlab-ci.yml

@@ -381,6 +381,8 @@
   # Gitaly has interactions with background migrations: https://gitlab.com/gitlab-org/gitlab/-/issues/336538
   - "GITALY_SERVER_VERSION"
   - "lib/gitlab/setup_helper.rb"
+  # Test-gap from https://gitlab.com/gitlab-org/quality/engineering-productivity/team/-/issues/275
+  - "{,ee/,jh/}lib/tasks/gitlab/seed/*.rake"
 
 # DB backup patterns
 .db-backup-patterns: &db-backup-patterns
@@ -611,7 +613,10 @@
   - qa/gdk/**/*
   - Gemfile.lock
   - yarn.lock
+  - scripts/frontend/postinstall.js
   - workhorse/**/*
+  - vendor/gems/**/*
+  - gems/**/*
   - VERSION
   - GITLAB_WORKHORSE_VERSION
   - GITLAB_METRICS_EXPORTER_VERSION
@@ -912,14 +917,16 @@
     - !reference [".qa:rules:package-and-test-never-run", rules]
     - <<: *if-default-branch-schedule-nightly # already executed in the 2-hourly schedule
       when: never
-    - <<: *if-default-branch-refs # Includes scheduled pipelines
+    - <<: *if-default-branch-refs
+    # Rebuild base only when relevant components change
+    - <<: *if-default-branch-refs
+      changes: *gdk-component-patterns
       variables:
         BUILD_GDK_BASE: "true"
-    # We want to also rebuild the base image if MRs change certain components.
     - <<: *if-merge-request
+      changes: *gdk-component-patterns
       variables:
         BUILD_GDK_BASE: "true"
-      changes: *gdk-component-patterns
     # The rest are included to be consistent with .qa:rules:e2e:test-on-gdk
     - <<: *if-merge-request-targeting-stable-branch
       changes: *setup-test-env-patterns