ci: Streamline CI browser playwright tests

[mydea]

This PR streamlines our browser integration tests a bit more:

1. We now only install chromium for playwright tests in most places. This may help cut down test run time a bit, as we do not need to install native dependencies for webkit and firefox everywhere.
2. I changed how we split the matrix jobs for the browser integration tests. Previously, we sharded this via playwright. Now, we only do this for esm tests, which we now only run in chromium, not all browsers. Only the full bundle tests are run in all browsers (they are considerably faster than the esm tests...), and there we now do not use sharding, but have one matrix job for chromium (default), one for webkit and one for firefox (where each can only install the native dependencies it needs).
3. I renamed the jobs a bit so that we can see a bit more of the job name in the Github UI... it still truncates but you see more than before, at least...
4. For all other playwright tests (e.g. e2e tests etc) we only install chromium, AFAIK we do not have any non-chromium tests anywhere there.

Some data points:

• E2E tests seem to be about 10-20% faster than before, by looking through traces here: https://sentry.sentry.io/performance/trace/c5c1c643f1db0e8dd97df658405c2035/?field=title&field=event.type&field=project&field=user.display&field=timestamp&name=All+Events&node=txn-8892bc908791478aba163dd3edd373b4&project=5899451&query=&sort=-timestamp&source=discover&statsPeriod=1h&timestamp=1723118364&yAxis=count%28%29
• For the playwright steps it's a bit harder to say as they are renamed, also they are not super consistent in execution time, we'll have to monitor it a bit afterwards, but subjectively it appears a bit shorter in most cases too.

[github-actions]

size-limit report 📦

Path	Size
@sentry/browser	22.47 KB (0%)
@sentry/browser (incl. Tracing)	34.26 KB (0%)
@sentry/browser (incl. Tracing, Replay)	70.31 KB (0%)
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags	63.64 KB (0%)
@sentry/browser (incl. Tracing, Replay with Canvas)	74.71 KB (0%)
@sentry/browser (incl. Tracing, Replay, Feedback)	87.32 KB (0%)
@sentry/browser (incl. Tracing, Replay, Feedback, metrics)	89.16 KB (0%)
@sentry/browser (incl. metrics)	26.77 KB (0%)
@sentry/browser (incl. Feedback)	39.42 KB (0%)
@sentry/browser (incl. sendFeedback)	27.09 KB (0%)
@sentry/browser (incl. FeedbackAsync)	31.75 KB (0%)
@sentry/react	25.24 KB (0%)
@sentry/react (incl. Tracing)	37.25 KB (0%)
@sentry/vue	26.62 KB (0%)
@sentry/vue (incl. Tracing)	36.1 KB (0%)
@sentry/svelte	22.61 KB (0%)
CDN Bundle	23.69 KB (0%)
CDN Bundle (incl. Tracing)	35.93 KB (0%)
CDN Bundle (incl. Tracing, Replay)	70.36 KB (0%)
CDN Bundle (incl. Tracing, Replay, Feedback)	75.61 KB (0%)
CDN Bundle - uncompressed	69.52 KB (0%)
CDN Bundle (incl. Tracing) - uncompressed	106.43 KB (0%)
CDN Bundle (incl. Tracing, Replay) - uncompressed	218.27 KB (0%)
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	231.16 KB (0%)
@sentry/nextjs (client)	37.1 KB (0%)
@sentry/sveltekit (client)	34.81 KB (0%)
@sentry/node	115.47 KB (+0.36% 🔺)
@sentry/node - without tracing	89.86 KB (+0.48% 🔺)
@sentry/aws-serverless	99.3 KB (+0.46% 🔺)

[BYK]

I'd really prefer if we kept Playwright as PW is not obvious for an onlooker.

[mydea]

The reason for this is that as of now this is so long that you often miss a lot of context:

making it very hard to find what kind of test this actually is :(

[mydea]

I named it back to Playwright ...!