Missing projectVersionKey resourceFixture for Hub /project-versions (15 nightly failures)

Problem

Nightly run #6598 has 15 failures in generated/camunda-hub/request-validation/secured/projectversions-validation-api-tests.spec.ts, all on updateProjectVersion: expected 400, got 404.

Root cause

Not a camunda-hub bug. updateProjectVersion (HubV2ProjectVersionController, commit 98ba1e5d3e) resolves/authorizes the {projectVersionKey} path variable before body parsing — same as every other Hub V2 update endpoint (e.g. updateWorkspace). workspaceKey has a resourceFixtures entry pointing to a real workspace the runner creates before tests, so its negative-body tests ride a valid resource into body validation (400). projectVersionKey has no fixture entry, so the generator falls back to filler ('x'/'1'), which correctly 404s before body validation ever runs.

Fix

Add a projectVersionKey → RV_FIXTURE_PROJECT_VERSION_KEY entry to configs/camunda-hub/request-validation.json's resourceFixtures map, and mint the fixture in scripts/e2e/run-hub.sh's make_fixtures(), following the same pattern as RV_FIXTURE_VERSION_KEY.

Failing tests (15)

All in generated/camunda-hub/request-validation/secured/projectversions-validation-api-tests.spec.ts, operationId updateProjectVersion.

🤖 Generated with Claude Code

Update configs/camunda-hub/request-validation.json and scripts/e2e/run-hub.sh, following the existing RV_FIXTURE_VERSION_KEY resource fixture pattern. Start by inspecting the resourceFixtures map and make_fixtures(); then run generated/camunda-hub/request-validation/secured/projectversions-validation-api-tests.spec.ts for updateProjectVersion. Done means the 15 cases receive the expected 400 responses instead of 404.