FE: Allow AI Catalog features to be at different maturity levels

About

There is a backend counterpart issue for this: #577764.

Currently, the entire AI Catalog is in Experiment.

We've decided that individual AI Catalog features should independently move from Experiment -> Beta -> GA.

Currently, agents are primed to be the first to move to Beta and then to GA. We expect flows, third party flows, and foundational agents to be maturing at different speeds.

Problem

The UX should also clearly differentiate which features are which maturity level.

Proposal

We will need the frontend to handle different features at different levels of maturity.

• Features should be hidden because the feature is Experiment/Beta and the project has not opted-in to Experimental/Beta AI Features
• The UI should label the maturity the individual features

Show/hide features

At the project-level, we should hide features that are Experimental/Beta if the project has not opted-in to Experiment/Beta AI features. The backend #577764 should make available to the frontend boolean properties it can use to determine if different AI Catalog features should be presented in the UI. This will be similar to how feature flag checks work.

Maturity labels per feature

We should signal the maturity level when viewing an item:

When creating/editing an item:

And when selecting different kinds of flows (if the different flows are at different maturity levels):