spec(fixtures): refresh bundled cloud_openapi.json from the live Redis Cloud spec

[joshrotenberg]

Summary

The vendored OpenAPI fixture in the repo is now behind the current upstream Redis Cloud spec and should be refreshed intentionally rather than drifting until another feature happens to touch it.

Evidence

Current repo fixture:

• tests/fixtures/cloud_openapi.json has 75 paths and 119 schemas

Current upstream spec (https://api.redislabs.com/v1/cloud-api-docs):

• 89 paths
• 137 schemas

That means the local fixture is missing at least:

• 14 paths
• 18 schemas

Examples of upstream-only paths

• /cost-report
• /cost-report/{costReportId}
• /subscriptions/{subscriptionId}/private-link
• /subscriptions/{subscriptionId}/private-link/principals
• /subscriptions/{subscriptionId}/private-link/endpoint-script
• /subscriptions/{subscriptionId}/resource-tags
• /subscriptions/{subscriptionId}/databases/{databaseId}/available-target-versions
• /fixed/subscriptions/{subscriptionId}/databases/{databaseId}/available-target-versions

Examples of upstream-only schemas

• CostReportCreateRequest
• BdbAvailableVersionsResponse
• TargetVersion
• SubscriptionResourceTagsUpdateRequest
• ResourceTag
• several PrivateLink* request/response schemas

Why this matters

• fixture-based tests and coverage assertions are only as good as the pinned spec
• stale fixtures can hide missing endpoints or schema drift
• issue docs: OpenAPI spec deltas - fields missing from official spec #40 is easier to work through when the local fixture is current

Acceptance criteria

• refresh tests/fixtures/cloud_openapi.json from the official source
• document any intentional local patching/delta handling
• update validation tests for the refreshed fixture
• link or fold remaining schema mismatches into issue docs: OpenAPI spec deltas - fields missing from official spec #40 or follow-up issues