1. Proposed title of this feature request
Allow OpenShift Service Mesh Operator to Use Custom Namespace and Prevent Duplicate Operator Installations When Enabling GatewayClass

2. What is the nature and description of the request?

• The ability to configure the namespace where the Service Mesh Operator should be installed when GatewayClass is enabled.
• Logic to detect and reuse an existing operator installation if one already exists in a custom namespace.

3. Why does the customer need this? (List the business requirements here)
Adherence to Best Practices, customers follow the guidance of avoiding the shared openshift-operators namespace for application-specific operators to maintain clean separation of responsibilities.

4. List any affected packages or components.

• OpenShift Service Mesh Operator
• Gateway API (GatewayClass) integration within Service Mesh
• Operator Lifecycle Manager (behavior triggered by Service Mesh installation logic)
• Namespace management workflows for operator deployment