docs: add verified quickstart manifests

[STRRL]

Problem

First time setup lacks ready to apply manifests for PostgreSQL and object storage. Building managed mode would add database and storage lifecycle ownership to the operator.

Solution

Keep dependencies external and add verified CloudNativePG, MinIO, Secret, and SupabaseProject manifests. This draft covers B1 and B2. Quickstart guide and README link will follow in round 2.

Major Changes

• Quickstart dependencies
  • Add CloudNativePG and MinIO configuration with matching credentials.
• Validation
  • Record successful kind validation, PostgreSQL TLS, MinIO bucket, Running project, and Studio HTTP 200.
• Architecture decision
  • Record why the operator uses external charts instead of managed mode.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: fb025a7f18

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Wait for component availability before testing Studio

On a fresh cluster or during slow image pulls, this wait can finish before any component pod is ready: reconcileAllComponents only creates/updates the Deployments, and internal/controller/supabaseproject_controller.go:158-168 immediately sets status.phase to Running without checking Deployment availability. The following kubectl get also succeeds when READY is zero, so the subsequent Kong port-forward can race with startup and make the documented validation intermittently fail; wait for each component Deployment to become Available (or use kubectl rollout status) before testing Studio.

Useful? React with 👍 / 👎.