fix(release-delete): enrich error for releases with health data (CLI-14K) (#749)

## Summary

- Catch the 400 "health data" `ApiError` from the Sentry API when
deleting a release and replace it with a clear, actionable message
explaining that releases with active session/crash-free data are
protected and must age out
- Add `test/commands/release/delete.test.ts` with 8 tests covering happy
path, dry-run, error enrichment, and passthrough for unrelated errors

Fixes [CLI-14K](https://sentry.sentry.io/issues/7409587075/)

### Before
```
Error: Failed to delete release '...': 400 Bad Request
  This release has health data and cannot be removed.
```

### After
```
Error: Release '...' has health data and cannot be deleted
  Releases with active session or crash-free data are protected by Sentry
  and cannot be removed via the API. The health data must age out before
  the release can be deleted.
  Release: https://acme.sentry.io/releases/1.0.0/
```

### Not in scope
- No server-side force-delete option exists in the Sentry API
- `--force` flag semantics unchanged (confirmation bypass only,
consistent across all delete commands)

Author: BYK