feat: Add db init and db status commands

[CalebBarnes]

Summary

This PR introduces a new db command to the Netlify CLI, enabling users to provision and manage production-ready Postgres databases with minimal effort.

Features

• Adds netlify db command with two primary subcommands:

  • db init - Initialize a new database and connects it to the current site
  • db status - Check the status of the database connection

• Seamless integration with Drizzle ORM:

  • Optional initialization of Drizzle configuration and schema boilerplate
  • Adds helpful database scripts to package.json
  • Auto-installs required Drizzle dependencies

• Flexible setup options:

  • Interactive mode with prompts for setup preferences
  • --assume-no flag for non-interactive setup (ideal for CI/AI tools)
  • --boilerplate=drizzle and --no-boilerplate flags to control ORM setup
  • --overwrite option to replace existing boilerplate files

Example Usage

# Initialize a database with interactive prompts
netlify db init

# Check database connection status
netlify db status

# Non-interactive setup for AI agents or CI environments
netlify db init --assume-no

# Initialize with Drizzle ORM and overwrite existing files
netlify db init --boilerplate=drizzle --overwrite

The implementation automatically handles extension installation, creating a database, and connecting it to the site via environment variables.

Documentation Generation Enhancement

I expanded the CLI documentation generator to support subcommands more robustly. Previously, subcommand docs were only generated if the command name contained a colon (:), such as dev:exec, which would be treated as a subcommand of dev. This approach missed subcommands defined as nested classes or those with explicit parent references.

Now, the docs generator also recognizes subcommands by checking the command's parent property, allowing it to correctly generate documentation for subcommands like those under the new db command without relying solely on colon-separated naming.

---

For us to review and ship your PR efficiently, please perform the following steps:

• Open a bug/issue before writing your code 🧑‍💻. This ensures we can discuss the changes and get feedback from everyone that should be involved. If you`re fixing a typo or something that`s on fire 🔥 (e.g. incident related), you can skip this step.
• Read the contribution guidelines 📖. This ensures your code follows our style guide and
  passes our tests.
• Update or add tests (if any source code was changed or added) 🧪
• Update or add documentation (if features were changed or added) 📝
• Make sure the status checks below are successful ✅

A picture of a cute animal (not mandatory, but encouraged)

[github-actions]

📊 Benchmark results

Comparing with 782de05

• Dependency count: 1,293 (no change)
• Package size: 316 MB ⬇️ 0.00% decrease vs. 782de05
• Number of ts-expect-error directives: 399 ⬆️ 0.50% increase vs. 782de05

[khendrikse]

We could add logic that if we notice that the site is not linked yet, we ask them if they want to do that, if they say yes we continue into that workflow?

[ndhoule]

submitting a few comments while I review the rest of the PR

[ndhoule]

Minor comments throughout; the only ones I feel strongly about are changing the --minimal flag to be more explanatory, and changing --drizzle to --orm/--boilerplate/something else.