fix(cli): stub transport in telemetry tests to prevent production event leakage

[sentry]

What was changed

In packages/cli/test/lib/telemetry.test.ts, mocked makeCompressedTransport from ../../src/lib/telemetry/zstd-transport.js using vi.mock so that it returns a no-op Sentry transport (createTransport(options, () => Promise.resolve({}))).

Why

Tests in telemetry.test.ts under the "with telemetry enabled" describe block deliberately unset SENTRY_CLI_NO_TELEMETRY to exercise real withTelemetry code paths, which constructs an active Sentry client pointing at the production SENTRY_CLI_DSN. When testing error handling (such as the deliberate CliError test fixture "Internal error: resolved issue missing org"), the error propagates through reportCliError and invokes Sentry.captureException.

Because makeCompressedTransport sends envelopes via node:http/https, the test suite's global fetch mock in test/preload.ts does not intercept it. Without a mocked transport, hundreds of fake test fixture errors were transmitted directly to the production CLI Sentry project across CI runs (tracked in CLI-299).

Stubbing the transport keeps the full capture pipeline, session scope logic, and existing captureException spies running as intended while guaranteeing no network payloads leave the process.

Fixes CLI-299

_{@sentry <feedback>: Autofix iterates on these changes
@sentry stop iterating: Autofix stops iterating on this run}

_{This PR was automatically generated by Sentry. You can adjust this setting at any time.}

[sentry-junior]

Looks good to me at 9d6a7076. No changes from me.

I reproduced the leak locally. I ran test/lib/telemetry.test.ts with a socket hook that records outbound connections and blocks them. Without this change, the file tries to connect to the CLI DSN's ingest host 27 times. With it, it makes no attempts. preload.ts only mocks fetch, and makeCompressedTransport sends over node:http/https, so the explanation in the description holds.

Stubbing the inner transport is the smallest fix. initSentry still wraps it with redactTelemetryEnvelope, so the capture, session and redaction code all still runs. The stub covers every enabled-SDK test in this file, not just the CliError fixture.

Tests: 112 of 113 tests pass locally. The failing test is createTracedDatabase > shows readonly warning when auto-repair fails, and it fails the same way on main in my sandbox because of the sandbox filesystem. All CI checks pass on this head, including test and sentry.