Sourcemap Debug Id Iteration V0

[HazAT]

Tracked by project: https://github.com/orgs/getsentry/projects/67/views/1

### JS SDK
- [x] Build POC CLI to inject bundle ID into generated bundles and source maps
- [x] Add logic to SDK to enrich stack frames in events with the corresponding bundle ID
- [ ] https://github.com/getsentry/sentry-javascript/issues/7161

## Ingest
- [x] `debug_id` field on stack frame needs to be preserved on event payload. Doesn't seem to be the case at the moment. (exact object path is `event.exception.values[].stacktrace-frames[].debug_id`) https://github.com/getsentry/relay/pull/1832

## Backend
- [ ] Source map upload endpoint needs to look for `debugId` field inside source map json.
- [ ] For each uploaded source map file that has a `debugId` field the endpoint needs to create some sort of index that maps “debug_id” —> “source map file”
- [ ] We should also explore if we want to provide an alternative endpoint to the existing source map upload endpoint because debug IDs are decoupled from releases

## Symbolication
- [ ] https://github.com/getsentry/team-stacktrace/issues/37

## CLI
- [x] Implement the small script added [here](https://github.com/getsentry/sentry-sourcemap-debug-id-cli), but in `sentry-cli`: https://github.com/getsentry/sentry-cli/issues/1467

## Docs
- [ ] Add instructions on how to use the new CLI command

[HazAT]

Fixes: getsentry/sentry-javascript#6423

[HazAT]

We are closing this since we created a project to keep track of everything
github.com/orgs/getsentry/projects/67/views/1