chore: regenerate models from upstream schemas

[stack72]

Summary

Automated regeneration of extension models from upstream provider schemas.

Changes

• aws: 1 files changed
• gcp: 46 files changed
• digitalocean: 1 files changed

Schema Sources

• AWS: CloudFormation Resource Schema
• GCP: Google Discovery Documents
• Hetzner: Hetzner Cloud OpenAPI spec
• DigitalOcean: DigitalOcean OpenAPI spec

Review Notes

• Files under model/ are auto-generated — review the manifest.yaml diffs for version changes
• CalVer versioning with content-based change detection ensures versions only bump when content changes
• Publishing happens automatically when this PR is merged (via the publish workflow)

[github-actions]

Code Review

Blocking Issues

None.

Summary

This is an automated regeneration PR — all changes are exclusively under model/ (auto-generated files). No hand-edited generated code is present.

The changes are consistent with a CI-driven codegen run against updated upstream provider schemas:

• GCP services (compute, accesscontextmanager, bigquerydatapolicy, firestore, networkservices, pubsub, sqladmin): CalVer version bumps with releaseNotes documenting updated resources. Three GCP Compute files deleted (globalvmextensionpolicies.ts, rolloutplans.ts, rollouts.ts) as these resources were removed from upstream schemas; corresponding entries also removed from manifest.yaml.
• AWS EC2 / DigitalOcean: Only stale releaseNotes removed — content-based change detection found no schema drift, so no version bump.

Manifest version formats (e.g. 2026.04.23.1 → 2026.05.03.1) follow the CalVer scheme documented in the codegen design docs.

[github-actions]

Code Review

Blocking Issues

None.

Summary

All changes are in auto-generated model/ files — no hand-written code was modified. The changes are consistent with automated schema regeneration from updated upstream provider schemas (GCP Discovery Documents, AWS CloudFormation, DigitalOcean OpenAPI):

• Version bumps from 2026.05.01.1 → 2026.05.04.1 across 48 packages
• New schema fields reflecting upstream API additions (e.g., dataGovernanceTag in bigquerydatapolicy)
• New methods reflecting new upstream API endpoints (e.g., update_memory_layer in bigtableadmin/instances_clusters)
• Deleted model files for resources removed from upstream schemas (globalvmextensionpolicies, rolloutplans, rollouts from compute)
• Description and enum cleanup matching upstream schema updates (e.g., ULL_POLICY removed from firewallpolicies enum)
• releaseNotes cleanup in manifests for previously-shipped versions

The any type usage is only in auto-generated files that carry // deno-lint-ignore-file no-explicit-any headers, which is exempt per CLAUDE.md. No codegen/, vault/, datastore/, or hand-written code was touched.