Feat: Add FF to hide beta tags for sessions

What does this MR do and why?

References

Related GitLab Issue:

Screenshots or screen recordings

Sessions, Triggers, Agents & Flows pages (when FF enabled)

Before	After

Catalog Pages

Before	After

How to set up and validate locally

For DAP/General Setup

• General DAP: https://docs.gitlab.com/development/duo_agent_platform/
• Assigning Duo to a group: https://docs.gitlab.com/development/ai_features/#run-gitlabduosetup-script
• Make sure you are in SaaS mode with export GITLAB_SIMULATE_SAAS=1 set in your env.runit file in your local gdk.

To Test on Agent Sessions page

1. Turn on the following feature flags: duo_workflow, duo_workflow_in_ci and ai_flow_triggers.
2. Navigate to a project with that has AI features enabled.
3. In the left side panel, you will see Automate with a tanuki icon. Select Sessions from the dropdown.

For Catalog Setup

1. Prerequisite: You have a Duo workflow-enabled project.
2. Enable the feature flags for the global_ai_catalog and flows (Product decisions)
3. If needed, add some seed data: Setting up GDK for Workflow Catalog Development

To Test Catalog pages

1. Visit http://gdk.test:3000/explore/ai-catalog/flows
2. Create a new flow
3. Edit a flow
4. Duplicate a flow
5. Enable flow in top level group
6. Visit flows page in a group (GROUP > Automate > Flows)
7. Visit detail page of a flow in a group
8. Visit flows page in a project (PROJECT > Automate > Flows)
9. Enable a flow from group
10. Visit flow detail page

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #581005