As an Admin, I should have the control to hide/show the AI Test Cases generation feature button

Description:
As an Administrator, I should be able to show or hide the AI Test Cases generation button in places like Test Repository and Requirements.

User friction:
Some organizations do not want to display the AI Test Cases generation feature button by default. They keep getting requests from users to enable the feature, creating unnecessary support overhead and distraction for teams not ready to use AI tools.

Steps to reproduce (right now) / Actual Result:

1. Log in as any user.

1. Navigate to the Test Repository or the Requirements page.

1. Observe that the Test Cases Beta (AI generation) button is always visible.
   Actual Result: Button appears for all users/orgs, leading to frequent support tickets requesting enablement or disablement.

IMPACT:
High support volume, user confusion in non-AI-ready teams, and delayed productivity as admins manually manage visibility via workarounds.

What would improve if solved:
Admins gain granular control to toggle the button on/off at the org level, reducing support requests to enable the feature, minimizing user friction, and allowing phased AI adoption.

Impact on stakeholders:

• Admins: Easier management, fewer tickets.

• End Users: Cleaner UI for non-AI users; feature available when needed.

• Org Leaders: Better control over tool rollout. Also, the limited AI credits can be judiciously used without user friction.

• Product Team: Reduced support costs, higher satisfaction scores.

Current workaround:
Admins instruct users to ignore the button or use custom roles/scripts to hide it via CSS hacks or browser extensions—not scalable or reliable.

CONTEXT & EXAMPLES:
In some regulated industries, orgs prefer manual test processes initially. AI button visibility prompts premature requests, overwhelming admins.

Concrete example:
A QA team at a bank sees the button daily but lacks AI approval. They submit tickets asking, "How to enable?" Admins spend hours responding instead of configuring.

Workaround risk:
The Jira Admins/ Request approvers will be exposed to more user friction if they do not want to allow the users to create Tests with the AI feature because the feature credits are limited.