Allow transitions to interrupt Suspensey commits

[acdlite]

I originally made it so that a Suspensey commit — i.e. a commit that's waiting for a stylesheet, image, or font to load before proceeding — could not be interrupted by transitions. My reasoning was that Suspensey commits always time out after a short interval, anyway, so if the incoming update isn't urgent, it's better to wait to commit the current frame instead of throwing it away.

I don't think this rationale was correct, for a few reasons. There are some cases where we'll suspend for a longer duration, like stylesheets — it's nearly always a bad idea to show content before its styles have loaded, so we're going to be extend this timeout to be really long.

But even in the case where the timeout is shorter, like fonts, if you get a new update, it's possible (even likely) that update will allow us to avoid showing a fallback, like by navigating to a different page. So we might as well try.

The behavior now matches our behavior for interrupting a suspended render phase (i.e. use), which makes sense because they're not that conceptually different.

[react-sizebot]

Comparing: 09c8d25...179bb4a

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.min.js	+0.01%	162.88 kB	162.90 kB	=	51.51 kB	51.51 kB
oss-experimental/react-dom/cjs/react-dom.production.min.js	+0.01%	164.42 kB	164.43 kB	=	52.00 kB	51.99 kB
facebook-www/ReactDOM-prod.classic.js	=	552.70 kB	552.72 kB	=	98.17 kB	98.16 kB
facebook-www/ReactDOM-prod.modern.js	=	536.55 kB	536.57 kB	=	95.53 kB	95.53 kB

Significant size changes

Includes any change greater than 0.2%:

(No significant changes)

Generated by 🚫 dangerJS against 179bb4a

[acdlite]

Approved as part of #26532