chore(typescript): Switch to --moduleResolution bundler, remove duplicate properties, remove @ts-expect-error comments

[DanielRosenwasser]

Related to #90413.

In order to cleanly measure relative performance improvements in the native port of the TypeScript compiler, this change removes some errors found by compiling with tsgo. Specifically:

• duplicate computed-name properties have been removed
• unnecessary @ts-expect-error comments have been removed (thanks to new moduleResolution settings`)
• deep imports into @emotion/styled have been replaced by updating an existing top-level import
• module resolution has been updated to bundler because
  • --moduleResolution node a.k.a. node10 will be deprecated in TypeScript 6.0
  • --moduleResolution nodenext will not work because many existing paths in import() calls lack a file extension
  • in reality, most files are processed by a bundler down the line (or a runtime like ts-node that has bundler-like resolution mechanics)

Legal Boilerplate

Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.

[github-actions]

🚨 Warning: This pull request contains Frontend and Backend changes!

It's discouraged to make changes to Sentry's Frontend and Backend in a single pull request. The Frontend and Backend are not atomically deployed. If the changes are interdependent of each other, they must be separated into two pull requests and be made forward or backwards compatible, such that the Backend or Frontend can be safely deployed independently.

Have questions? Please ask in the #discuss-dev-infra channel.

[ryan953]

@DanielRosenwasser I'm seeing the following output, but its obvs set to be "module": "preserve" & "moduleResolution": "bundler" in the PR. I'll look deeper in the morning to make sure that the PR branch changes are being picked up and applied in CI.

$ node scripts/test.js --ci --maxWorkers=100% --colors --forceExit
Error: Jest: Failed to parse the TypeScript config file /home/runner/work/sentry/sentry/jest.config.ts
  TSError: ⨯ Unable to compile TypeScript:
error TS5095: Option 'bundler' can only be used when 'module' is set to 'preserve' or to 'es[20](https://github.com/getsentry/sentry/actions/runs/15033225703/job/42249995049?pr=91686#step:6:21)15' or later.

from: https://github.com/getsentry/sentry/actions/runs/15033225703/job/42249995049?pr=91686

[DanielRosenwasser]

I'm seeing the following output, but its obvs set to be "module": "preserve" & "moduleResolution": "bundler" in the PR.

I think this is resolved in Jest 30 (not released yet!):

• https://github.com/jestjs/jest/releases/tag/v30.0.0-alpha.5
• fix: allow Node16/NodeNext/Bundler moduleResolution in project's tsconfig jestjs/jest#14739

[scttcper]

@DanielRosenwasser that jest pr was helpful, i think you can force that mode just for ts-node. We only use ts-node for webpack and jest configs and this would kinda backport the change.

  "ts-node": {
    "transpileOnly": true,
    "compilerOptions": {
      "moduleResolution": "Node10"
    }
  }