test(8.10): run bitnami→companion migration hook for MT and document-store modular upgrades

[eamonnmoloney]

Which problem does the PR fix?

The SM Nightly 8.10 Upgrade Minor MT run fails: after the 8.9→8.10 modular
upgrade, demo/bart/lisa hit "You don't have access to this component" in
Operate, and /v2/authentication/me returns empty roles and tenants.

Originating nightly run:
https://github.com/camunda/c8-cross-component-e2e-tests/actions/runs/27930811972

Root cause: the post-infra-bitnami-migration hook — which migrates the bundled
(Bitnami) Keycloak realm and the Elasticsearch authorization indices onto the
companion services before the chart upgrade removes the bundled subcharts —
was wired only to qa-elasticsearch-upg-modular when it was introduced in #6343.
The MT and document-store modular-upgrade scenarios were left without it, so the
companion Elasticsearch is never seeded with the 8.9 authorization data. After
the upgrade the orchestration reads an effectively empty authorization store.

This is why the plain ES modular upgrade is green while MT / document-store are red.

What's in this PR?

Adds post-infra: post-infra-bitnami-migration to the Elasticsearch-backed
modular-upgrade scenarios that were missing it:

• qa-elasticsearch-mt-upg-modular.yaml
• qa-document-store-upg-modular-gke.yaml
• qa-document-store-upg-modular-eks.yaml

Registry snapshot regenerated via make go.update-registry-golden.

OpenSearch modular upgrade is intentionally out of scope here: the hook is
Elasticsearch-specific, and that scenario shows a separate /identity login
failure that needs its own fix.

Verification (live GKE repro): installed 8.9-MT (bundled), ran the
modular-upgrade-minor flow, and inspected the companion Elasticsearch. Without
the hook the companion ES had 0 authorizations / 0 tenants and the admin
role kept only the newly-seeded mapping rules (demo and the 8.9 members were
absent) — reproducing the nightly failure. The plain ES modular scenario, which
already carries the hook, is green.

Checklist

Please make sure to follow our Contributing Guide.

Before opening the PR:

• In the repo's root dir, run make go.update-golden-only.
• There is no other open pull request for the same update/change.
• Tests for charts are added (if needed).
• In-repo documentation are updated (if needed).

After opening the PR:

• Did you sign our CLA (Contributor License Agreement)? It will show once you open the PR.
• Did all checks/tests pass in the PR?

[Copilot]

Pull request overview

This PR fixes missing lifecycle wiring in Camunda Platform Helm 8.10 CI scenario registry so that modular upgrade scenarios that start from bundled Bitnami services properly run the Bitnami → companion migration before the chart upgrade removes the bundled subcharts.

Changes:

• Add post-infra: post-infra-bitnami-migration to the MT and document-store modular-upgrade-minor Elasticsearch-backed QA scenarios.
• Regenerate the test/ci/registry-snapshot.yaml golden to reflect the added post-infra hook blocks for those scenarios.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File	Description
charts/camunda-platform-8.10/test/ci/registry/scenarios/qa-elasticsearch-mt-upg-modular.yaml	Adds the post-infra migration hook to the MT modular-upgrade scenario.
charts/camunda-platform-8.10/test/ci/registry/scenarios/qa-document-store-upg-modular-gke.yaml	Adds the post-infra migration hook to the document-store modular-upgrade scenario on GKE.
charts/camunda-platform-8.10/test/ci/registry/scenarios/qa-document-store-upg-modular-eks.yaml	Adds the post-infra migration hook to the document-store modular-upgrade scenario on EKS.
charts/camunda-platform-8.10/test/ci/registry-snapshot.yaml	Updates the registry snapshot to include the new post-infra hook entries for the affected scenarios.