Chronon registration in #6188 added Python store types without adding them to the operator's persistence allowlists. A FeatureStore using type: chronon is rejected, and the Python/operator data-source consistency suite fails for both online and offline stores.

Add chronon to both persistence enums and validation lists in the v1 and v1alpha1 APIs. Regenerate the CRD, installer, and bundle schemas, and refresh the secret baseline's shifted line numbers.

Ray, DuckDB, and registration CI also stop before tests because the earlier GLIDE extra change left Feast's local-package metadata stale in pixi.lock. Synchronize the GLIDE requirement and CI-extra membership. No resolved package versions change.

Validation:

• Reproduced two missing-chronon failures with make -C infra/feast-operator test-datasources; all three checks pass after the fix.
• make -C infra/feast-operator build-installer and make -C infra/feast-operator bundle pass.
• All 24 generated online/offline persistence enums include Chronon.
• Scoped pre-commit checks and git diff --check pass.
• Pixi 0.75.0 lock --dry-run --check confirms the updated lockfile is current.
• Final-commit CI passes: Linux/macOS Python unit matrix, Go/UI unit tests, lint/security/smoke, local integration including operator data-source parity, Ray, DuckDB, registry REST, remote RBAC, and operator tests including end-to-end, previous-version, and upgrade coverage.
• Both local and cloud registration jobs pass on the rerun that checks out the updated PR merge ref.