Run all tests with devtools attached

[eps1lon]

Stacked on #34464

We'll probably need to start with an allow-list first because some tests are not compatible (specifically ones testing RDT integration).

Maybe this will just be an extra config if it's too slow. Ideally we take a store snapshot after each act. Not sure yet how that'll look to not be too disruptive.

Need to go through some of the instrumentation failures this is currently reporting. The ones related to react-test-renderer I'm not too worried. That renderer is deprecated anyway.

[react-sizebot]

Comparing: b1c519f...e8c6afb

Critical size changes

Includes critical production bundles, as well as any change greater than 2%:

Name	+/-	Base	Current	+/- gzip	Base gzip	Current gzip
oss-stable/react-dom/cjs/react-dom.production.js	=	6.68 kB	6.68 kB	+0.05%	1.83 kB	1.83 kB
oss-stable/react-dom/cjs/react-dom-client.production.js	=	530.65 kB	530.65 kB	=	93.49 kB	93.49 kB
oss-experimental/react-dom/cjs/react-dom.production.js	=	6.69 kB	6.69 kB	=	1.83 kB	1.83 kB
oss-experimental/react-dom/cjs/react-dom-client.production.js	=	658.20 kB	658.20 kB	=	115.79 kB	115.79 kB
facebook-www/ReactDOM-prod.classic.js	=	682.36 kB	682.36 kB	=	119.83 kB	119.83 kB
facebook-www/ReactDOM-prod.modern.js	=	672.79 kB	672.79 kB	=	118.14 kB	118.13 kB

Significant size changes

Includes any change greater than 0.2%:

(No significant changes)

Generated by 🚫 dangerJS against e8c6afb

[rickhanlonii]

Can we create a separate test variant that runs with dev tools attached? We should test both paths so we don't accidentally depend on devtools for behavior.

[rickhanlonii]

With a separate variant, we will also be able to exclude certain paths (like the linter) and use the @gate pragma to disable broken tests until they're fixed.

[eps1lon]

This is a draft for a reason. I just needed a picture from CI