fix: grouped pretty print status output

[gregnr]

This updates the pretty printed output from supabase start and supabase status to be a bit more user friendly, especially for newcomers. Specifically:

• Groups info into tables by category (dev tools, apis, database, auth keys, s3)
• Colorizes value based on type (link, key, text)
• Adds API URLs for REST and Edge Functions

Implementation-wise I tried a few different table renderers (including manual), but tablewriter ended up being the most straightforward and least buggy.

Testing

1. Clone this branch feat/pretty-print-output.
2. Run go run . start - observe the new output.
3. Also run go run . status to see the same output.

[coveralls]

Pull Request Test Coverage Report for Build 19694860430

Details

• 92 of 102 (90.2%) changed or added relevant lines in 2 files are covered.
• 8 unchanged lines in 2 files lost coverage.
• Overall coverage increased (+0.1%) to 55.536%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
internal/status/status.go	89	99	89.9%

Files with Coverage Reduction	New Missed Lines	%
internal/status/status.go	3	77.41%
internal/gen/keys/keys.go	5	12.9%

Totals
Change from base Build 19692043920:	0.1%
Covered Lines:	6721
Relevant Lines:	12102

---

💛 - Coveralls

[A-F-V]

Is there a way to get the old rendering of info? This makes parsing much much harder....
Documentation is now out of date: https://supabase.com/docs/reference/cli/supabase-status

[gregnr]

Hey @A-F-V, thanks for the heads up on docs, we'll update this.

If you need to parse the info programmatically, you can use the --output (-o) flag to output the info as env vars, JSON, TOML, or YAML:

supabase status -o env

$ supabase status --help
Show status of local Supabase containers

Usage:
  supabase status [flags]

Examples:
  supabase status -o env --override-name api.url=NEXT_PUBLIC_SUPABASE_URL
  supabase status -o json

Flags:
  -h, --help                    help for status
      --override-name strings   Override specific variable names.

Global Flags:
      --create-ticket                                  create a support ticket for any CLI error
      --debug                                          output debug logs to stderr
      --dns-resolver [ native | https ]                lookup domain names using the specified resolver (default native)
      --experimental                                   enable experimental features
      --network-id string                              use the specified docker network instead of a generated one
  -o, --output [ env | pretty | json | toml | yaml ]   output format of status variables (default pretty)
      --profile string                                 use a specific profile for connecting to Supabase API (default "supabase")
      --workdir string                                 path to a Supabase project directory
      --yes                                            answer yes to all prompts

Let me know if this works for you.