chore: Deduplicate yarn.lock to collapse redundant transitive dependency copies

[antonis]

Summary

yarn dedupe --check reports 570 transitive packages that could be collapsed onto a single, already-resolved higher version. This is lockfile-only hygiene to reduce node_modules footprint and speed up installs for contributors and CI.

Scope & safety (verified)

This is not user-facing and not a breaking change:

• yarn.lock is not included in the published npm tarball (npm pack --dry-run → no lockfile present).
• No bundled dependencies — consumers resolve their own tree from @sentry/react-native's package.json ranges, never from this repo's lockfile.
• All 570 affected packages are dev/build tooling (@babel/*, semver, debug, tslib, resolve, es-abstract, and assorted shim helpers). No runtime @sentry/* dependency is affected.
• Every version move is within the same semver major (e.g. semver 7.6.3 → 7.8.5, @babel/types 7.25.4 → 7.29.7, tslib 2.7.0 → 2.8.1) — i.e. versions already permitted by the existing ^/~ ranges that a clean-cache install would land on anyway.

Proposed change

yarn dedupe
# commit the updated yarn.lock

Acceptance criteria

• yarn dedupe --check reports no further duplicates
• yarn build passes
• yarn test passes
• cd packages/core && yarn api-report:check passes (no public API drift)
• Only yarn.lock is modified

Notes

• Priority: low. This is optional cleanup, not a fix — nothing is broken without it.
• No CHANGELOG.md entry needed (internal-only, no user-visible change).

[linear-code]

RN-765