As a cluster admin installing an extension, I would like to configure registry+v1 bundle installations much in the same way I could with v0's Subscription's .spec.config, because I would like to deploy the extension in a way to better matches my cluster's peculiarities (e.g. ensure the extension's pods end up on specific infrastructure, use more/less resource, etc.)

A/C:

• Add DeploymentConfig type definition to api/v1 (copying OLMv0's SubscriptionConfig structure)
• Generate frozen JSON schema from Kubernetes core/v1 and apps/v1 OpenAPI specs for DeploymentConfig fields
• Integrate DeploymentConfig schema into BundleConfig validation (leveraging OPRUN-4112's infrastructure)
• Update ClusterExtension controller to:

                   - Extract deploymentConfig from .spec.config.inline

                   - Pass deploymentConfig to renderer via WithDeploymentConfig() option

•  Validation errors must provide clear, semantic feedback to users
• Add unit tests for schema validation with various DeploymentConfig scenarios