Support non-Node devs: allow install.sh to trigger the setup wizard

## Summary `sentry init` (the SDK setup wizard) is only accessible to developers who have Node installed, since the canonical invocation is `npx @sentry/wizard`. Developers working in non-Node ecosystems (PHP/Laravel, Python, Ruby, etc.) have no frictionless path to run the wizard without first installing Node. ## Current behavior The wizard is distributed as an npm package and invoked via `npx @sentry/wizard`. The `sentry-cli` install script (`install.sh`) downloads and installs the CLI binary but does not expose the wizard flow. ## Gap Requiring Node as a prerequisite excludes a large share of backend/non-JS developers—precisely the audience that would benefit most from an onboarding wizard. Asking them to install Node just to run setup is a meaningful friction point. ## Options | Approach | Tradeoff | |---|---| | Extend `install.sh` to accept a `--init` flag: download CLI to a temp path, run `sentry-cli wizard`, then clean up | Minimal surface change; reuses the existing curl-based install entry point | | Add a dedicated `init.sh` one-liner that fetches the binary, runs the wizard, and exits | Cleaner separation, but a second script to maintain | | Bundle wizard logic directly into `sentry-cli` as a subcommand | Most robust long-term; no Node dependency at all, but highest implementation cost | ## Recommendation Short-term: extend `install.sh` with an optional `--init` / `SENTRY_INIT=1` env var trigger that downloads the CLI binary to a temp location, runs `sentry-cli wizard`, and optionally cleans up afterward. This gives any developer a single curl command to reach the wizard without permanently installing anything. Long-term: evaluate moving wizard logic into `sentry-cli` itself so the experience is fully self-contained. Action taken on behalf of Miguel Betegon.