[Feature flag] Enable `value_stream_analytics_filter_bar` feature

What

Remove the :value_stream_analytics_filter_bar feature flag that is introduced in #217943 (closed).

Related to #12525 (closed)

Owners

• Team: g_manage_analytics
• Most appropriate slack channel to reach out to: #g_manage_analytics
• Best individual to reach out to: @ekigbo @wortschi

Expectations

• A filter bar will be made available for value stream analytics
• Values selected in the filter bar will be reflected in the query parameters for page to enable bookmarking

### What are we expecting to happen?

What might happen if this goes wrong?

What can we monitor to detect problems with this?

Beta groups/projects

If applicable, any groups/projects that are happy to have this feature turned on early. Some organizations may wish to test big changes they are interested in with a small subset of users ahead of time for example.

• gitlab-org/manage
• gitlab-org

Roll Out Steps

• Enable on staging
  • gitlab-org
  • All groups
• Test on staging
• Ensure that documentation has been updated
• Enable on GitLab.com for individual groups/projects listed above and verify behaviour
• Coordinate a time to enable the flag with #production and #g_delivery on slack.
• Announce on the issue an estimated time this will be enabled on GitLab.com
• Enable on GitLab.com by running chatops command in #production
  • Enable for gitlab-org/manage
  • Enable for gitlab-org
  • Enable for All groups
• Cross post chatops slack command to #support_gitlab-com (more guidance when this is necessary in the dev docs) and in your team channel
• Announce on the issue that the flag has been enabled
• Remove feature flag and add changelog entry
• After the flag removal is deployed, clean up the feature flag by running chatops command in #production channel