Cortex Cloud: Why does Cortex Cloud creates a new identity domain when running the onboarding script in OCI

Cortex Cloud Onboarding scripts create a new identity domain in OCI

**Product_versions**
Cortex Cloud 2.1

Cortex Cloud license on Cortex XSIAM and Cortex XDR

An OCI limitation restricts one trust policy per IdP per domain. The Cortex XSIAM WIF implementation relies on "accounts.google.com". When multiple Cortex tenants are linked to a single OCI tenancy or another tool already uses Google as an IdP in the same domain, attempting to add a second trust policy results in a 409 Conflict, necessitating the creation of a new identity domain.

**REMEDIATION_PLAN**
Creating a separate identity domain during OCI integration to ensure clean and conflict-free onboarding for Cortex XSIAM.

**PREVENTIVE_MEASURES**
Creating a separate identity domain during OCI integration to prevent 409 Conflict errors caused by OCI's trust policy limitation.

This change will help us in the future when we implement Compartment-level onboarding from the same OCI tenancy.