Rework GCP deployment doc for VM install, align with AWS/Azure

[sklarsa]

Summary

Compute Engine no longer supports deploying a container as the VM OS (the Deploy Container option at VM creation), so the GCP deployment guide is reworked to:

• Create a standard Ubuntu 24.04 VM and install QuestDB over SSH using the release binary, mirroring the Azure guide's install flow.
• Adopt the AWS/Azure page structure: Quick reference → Infrastructure (instance sizing, storage, networking) → Deployment → Security → Operations → Enterprise on GCP.
• Fold the GCP-specific storage content (Hyperdisk Balanced, Filestore, GCS, NetApp Volumes) into the new sections, with Filestore/NetApp/GCS now grouped under Enterprise replication.
• Remove the stale Pulumi example (Ubuntu 20.04, raw docker run, hardcoded credentials; AWS/Azure have no IaC section).
• Add a note explaining that container-as-VM-OS is no longer supported.
• Delete the orphaned create-vm-docker.webp (deprecated flow) and instance-available.webp screenshots.

🤖 Generated with Claude Code

[github-actions]

🚀 Build success!

Latest successful preview: https://preview-470--questdb-documentation.netlify.app/docs/

Commit SHA: 00eaff8

📦 Build generates a preview & updates link on each commit.

[sklarsa]

  Re-review: update-gcp-deployment-vm-install (post-commit)

  Verdict

  Approve. The page is technically correct, consistently structured, builds clean, and the previously-flagged issues
  are all resolved. No blocking issues, no remaining nits worth holding the merge for. Ready to merge.

  ---
  Pillar-by-pillar

  Pillar 0 — Technical correctness: ✅
  - gcloud commands are internally consistent: instance create + disk create + attach-disk all use questdb-data as
  both disk name and device name, matching the /dev/disk/by-id/google-questdb-data path in the prepare step (:296).
  - Firewall console steps (8812,9000, :244) and gcloud (tcp:9000,tcp:8812, :268) agree.
  - Disk units now consistent (GiB throughout console + CLI).
  - Ubuntu 24.04 x86_64 image family ubuntu-2404-lts-amd64 / project ubuntu-os-cloud is correct, and matches the
  ARM-avoidance warning.
  - mkfs.ext4, fstab nofail, and discard options are sound for a Hyperdisk data disk.

  Pillar 1 — Placement and findability: ✅ Already in sidebars.js:691 under deployment; no change needed. Sits
  alongside aws.md/azure.md at the right depth.

  Pillar 2 — Humans + LLMs: ✅ Strong. Quick reference table up top gives an LLM the whole answer at a glance; dual
  console/gcloud paths; concrete "deployment is working when…" checklist (:347-351). Information flows intent →
  infra → deploy → secure → operate without backtracking.

  Pillar 3 — Examples: ✅ N/A as SQL-heavy page, but every command block is copy-pasteable and env-var
  parameterized. No invented schemas.

  Pillar 4 — SEO/LLM: ✅ Description frontmatter is specific (names Compute Engine, sizing, storage, networking).
  Headings are descriptive and keyword-bearing.

  Pillar 5 — Syntax diagrams: N/A — this is a deployment guide, not a SQL reference page.