fix(remix): Make sure the domain is created before running.

[onurtemizkan]

Resolves: #6821

This problem appears not to be a flaky test, it's a node bug recurring on certain versions, which apparently happens rarely, and our testing environment (high concurrency in a small container maybe) seems to amplify its frequency.

Looks like this can happen when the domain is used right after the creation, which is the case in our Remix implementation. And the proposed workaround seems to resolve it with this PR. (8 CI runs without errors here, only failed case is #6848, will be addressed with another PR).

For reference:
#2089
nodejs/node#30122
nodejs/node#40999

[github-actions]

size-limit report 📦

Path	Size
@sentry/browser - ES5 CDN Bundle (gzipped + minified)	19.82 KB (+0.01% 🔺)
@sentry/browser - ES5 CDN Bundle (minified)	61.47 KB (0%)
@sentry/browser - ES6 CDN Bundle (gzipped + minified)	18.5 KB (+0.02% 🔺)
@sentry/browser - ES6 CDN Bundle (minified)	54.77 KB (0%)
@sentry/browser - Webpack (gzipped + minified)	20.21 KB (0%)
@sentry/browser - Webpack (minified)	66.17 KB (0%)
@sentry/react - Webpack (gzipped + minified)	20.24 KB (0%)
@sentry/nextjs Client - Webpack (gzipped + minified)	47.48 KB (0%)
@sentry/browser + @sentry/tracing - ES5 CDN Bundle (gzipped + minified)	26.74 KB (+0.01% 🔺)
@sentry/browser + @sentry/tracing - ES6 CDN Bundle (gzipped + minified)	25.03 KB (+0.02% 🔺)
@sentry/replay ES6 CDN Bundle (gzipped + minified)	43.12 KB (-1.16% 🔽)
@sentry/replay - Webpack (gzipped + minified)	37.83 KB (-1.57% 🔽)
@sentry/browser + @sentry/tracing + @sentry/replay - ES6 CDN Bundle (gzipped + minified)	60.37 KB (-0.86% 🔽)

[AbhiPrasad]

Makes sense to me - and another reason why we should get rid of domains soon. Thanks for taking a look Onur!