fix(cli): replace init with config command

[dannysteenman]

Summary

• What changed?
  • Replaced the legacy root init command with a dedicated config command.
  • Added cloudburn config --init to write a starter config, cloudburn config --print to print the discovered config file, and cloudburn config --print-template to print the starter template without writing.
  • Updated CLI tests, completion coverage, README, architecture docs, config reference, and package guidance to match the new command surface.
• Why was this needed?
  • The CLI config workflow was inconsistent and still carried the older init compatibility shape.
  • This makes the command surface match the intended config-focused workflow and removes the stale init contract entirely.

Diagram

flowchart TD
  A["cloudburn config --init"] --> B["Write starter .cloudburn.yml"]
  C["cloudburn config --print"] --> D["Discover or use explicit config path"]
  D --> E["Print current YAML"]
  F["cloudburn config --print-template"] --> G["Print starter template"]

Loading

Scope

• cloudburn (cli)
• @cloudburn/sdk
• @cloudburn/rules
• docs/community files

Release Notes

• Added a .changeset/*.md file for published package changes
• No published package changes in this PR

Verification

• pnpm lint
• pnpm typecheck
• pnpm test
• pnpm build
• pnpm verify

Boundary Checks

• No engine/parser/provider logic added to @cloudburn/rules
• CLI delegates scan logic to SDK
• README/CONTRIBUTING/docs updated when behavior changed