[minor] support new AI Service tenant operator

[boonware]

Issue

MASAIB-1246

Details

• Support the new AI Service namespace-scoped tenant operator for 9.2. Various charts now contain conditional rendering by checking the catalog channel for a "9.2." prefix to determine if we are installing AI Service 9.2 or later. For 9.2 we install the new operator and perform migration steps.
• Migration is orchestrated by using pre-sync, sync and post-sync jobs. A pre-sync job locks the tenant upgrade by checking the AI Service namespace to confirm the 9.1 tenant operator is no longer deployed. This locking is necessary as moving the AIServiceTenant CR from the AI Service namespace to the tenant namespace would trigger the operator's finalizer so we must wait for the operator to be gone.
• Migration also involves moving some secrets into the tenant namespace.
• Updated the existing job that copies the S3 secret and entitlement secret to the tenant namespace to ensure the secrets are not tracked by ArgoCD. Doing so causes the tenant application to show out-of-sync as these secrets are not tracked in Git (the copies).

Test Results

• To confirm the environment is working as expected it is sufficient to get a single passing model test. This confirms that the AI Broker API authentication is working as expected with the resources moved around and the new API key as generated by the operator. For both 9.1 and 9.2 I have run the Similarity model test suite against the cluster and it passed in both cases.
• The changes have been tested for both migrating an existing tenant and provisioning a new tenant.