v6 upgrade-experience gaps: large bundled CRDs need server-side apply; ESO v1beta1 dropped; RC value renames

Describe the bug:

Three smaller, related rough edges surfaced upgrading 5.x → 6.x. Filing together; happy to split.

1. Bundled CRDs exceed the client-side-apply annotation limit and require server-side apply.
The ESO 2.4.x clustersecretstores/secretstores CRDs (like kube-prometheus-stack's) exceed kubectl's 262144-byte last-applied-configuration annotation limit, so a plain kubectl apply fails:

metadata.annotations: Too long: must have at most 262144 bytes

Anyone applying these out-of-band (dry-run gates, pre-flight CRD installs) must know to use kubectl apply --server-side. This isn't shipped or documented.
Ask: install bundled CRDs with server-side apply, and document the SSA requirement.

2. The bundled ESO drops the external-secrets.io/v1beta1 served version, with no migration note.
Because v6 now owns ESO, its API-version bump becomes apl-core's upgrade contract. Every existing ExternalSecret/ClusterSecretStore we had was v1beta1; v6's ESO serves v1 only, so they 404 mid-cutover if not converted first. There's no upgrade note or conversion guidance.
Ask: call out the served-version removal prominently in the v6 upgrade notes and point to a conversion path (or ship one).

3. Breaking chart-value renames landed between RCs of the same major, with no changelog.
imageName/otomi.useORCS → operator.image.repository, and the removal of the kms.sops block and operator.gitOrg/operator.gitRepo, all landed silently in the rc.12 → GA delta. We happened not to override those, but an adopter who did would break on what looks like a "straight re-pin."
Ask: changelog / migration notes for value-schema changes, even within a major's RC line.

Expected behavior: apl-core-owned CRDs install cleanly out-of-band; API-version and value-schema changes across the v6 line are documented as upgrade steps.

Cluster(s): Linode / Akamai LKE-Enterprise.

Versions: apl-core v6.0.0-rc.12 → 6.0.0 GA.

Start by locating the bundled CRD installation path, v6 upgrade notes, changelog, and chart-value definitions; reproduce the client-side apply failure and inspect the served ESO API versions. Done means bundled CRDs install out-of-band, the v6 notes explain the v1beta1 conversion, and the RC-to-GA value renames and removals are documented.