feat(raes): qualify additional released infrastructure kits as needed

[Brad-Edwards]

Goal

Qualify additional released infrastructure kits when a selected Shifter scenario needs them. The first GCP canary and useful scenario are covered by #2082. This issue holds broader kit coverage until there is a concrete adoption need.

Use the released RAES/environment-pack contracts from OpenRAE/env-packs#190 and OpenRAE/reference-packs#2. Do not add a Shifter-specific kit runtime API or copy kit metadata into this repository.

For each selected kit

• Name the scenario and released kit artifact that require it.
• Compose an ordinary released environment pack and admit it through Shifter's declared capability profile.
• Verify the infrastructure, access, services, and relationships Shifter claims to realize, including launch, readiness, and teardown where applicable.
• Add a regression test and a short proof record. If a capability is missing, track the exact Shifter gap with a failing test.

The original issue history contains the full published-kit inventory. Catalog-wide parity is not a prerequisite for the first GCP scenario.

[Brad-Edwards]

Adoption review clarification — #2080 (2026-09-05)

Retain this as the broad infrastructure-kit qualification program. The first GCP adoption gate uses only the small released cohort selected in #2082/#2091. List supported, rejected and unqualified kits with exact artifacts and evidence; do not make every published kit a prerequisite for the first useful release. Additional envelope expansion requires a concrete selected scenario and independent lifecycle/participant evidence. AWS and additional participant-control mechanisms remain separate qualifications.