Extend the registry+v1 bundle rendering capabilities to support SubscriptionConfig (from OLMv0) for deployment customization, following the design laid out in the RFC: https://docs.google.com/document/d/18O4qBvu5I4WIJgo5KU1opyUKcrfgk64xsI3tyXxmVEU/edit?tab=t.0

AC: 

1. Schema Generation Infrastructure:

    - Implement schema generator that introspects v1alpha1.SubscriptionConfig Go struct from github.com/operator-framework/api

    - Handle embedded Kubernetes core types (corev1.Toleration, corev1.ResourceRequirements, corev1.Affinity, etc.)

    - Generate frozen JSON schema artifact at build time

    - Add Makefile target update-deploymentConfig-schema to regenerate schema when dependencies update

    - Unit tests for schema generator

2. Integrate SubscriptionConfig into BundleConfig validation:

   - Extend inline configuration base schema to include optional deploymentConfig field

   - Merge generated SubscriptionConfig schema into bundle configuration schema

   - Leverage existing schema validation infrastructure (from OPRUN-4112)

   - Validation errors provide clear, semantic feedback

   - Unit tests for schema validation with various deploymentConfig scenarios