build(ui): Add rspack as webpack alternative

[scttcper]

Building off the work done in #61475 I think the plan would be to use this as a dev-ui replacement until we're more confident and can setup the getsentry repo as well (if you aren't familiar we have another repo with billing pages etc).

Potential adoption roadmap

1. merge rspack as optional dev only command yarn dev-ui-rspack
2. make rspack default for dev-ui
3. use rspack for acceptance tests
4. build production with rspack
5. remove webpack

Summary

	Webpack	Rspack
HMR Time	4s	607ms
Dev Memory Usage	3.85 GB	2.8 GB
Build Production	131.53s	39.42s

RSPACK + SENTRY TODO (updated Oct 7th, 2024)

• Investigate emotion autoLabel in development mode. Currently set to autoLabel: 'always', Could just set label setting based on node_env.
• Add back webpack in order to merge (getsentry repo will block until it can accept a rspack file instead of webpack)
• Figure out a path forward for translation string extraction that use webpack + babel's AST make build-js-po
• Chartcuterie is failing for some reason

Thanks @hardfist for helping with this PR!

[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.

[scttcper]

Just realized its working for me locally because i fixed platformicons locally will need to publish a fix to the svg paths there

[codecov]

❌ 1 Tests Failed:

Tests completed	Failed	Passed	Skipped
10290	1	10289	9

View the full list of 1 ❄️ flaky tests

Sentry Application Details Editing an existing public Sentry App with a scope error handles client secret rotation

Flake rate in main: 18.18% (Passed 9 times, Failed 2 times)

Stack Traces | 0.405s run time

TestingLibraryElementError: Unable to find an element with the text: This will be the only time your client secret is visible!. This could be because the text is broken up by multiple elements. In this case, you can provide a function for your text matcher to make your matcher more flexible.

Ignored nodes: comments, script, style
...
    at Object.getElementError (.../sentry/sentry/node_modules/@.../dom/dist/config.js:37:19)
    at .../sentry/sentry/node_modules/@.../dom/dist/query-helpers.js:76:38
    at .../sentry/sentry/node_modules/@.../dom/dist/query-helpers.js:52:17
    at .../sentry/sentry/node_modules/@.../dom/dist/query-helpers.js:95:19
    at Object.<anonymous> (.../settings/organizationDeveloperSettings/sentryApplicationDetails.spec.tsx:591:42)

To view more test analytics, go to the Test Analytics Dashboard
_{📋 Got 3 mins? Take this short survey to help us improve Test Analytics.}

[evanpurkhiser]

slam it

[JonasBa]

Those HMR numbers look 🔥

[JonasBa]

Outside of the scope of this PR, but it would be interesting if we could time this locale procedure to see how much it contributes to the startup cost.