Fix useDeferredValue getting stuck

[gaearon]

Fixes #35821

Written/debugged by Claude.

Test Plan

• Verify undoing the source fix fails the newly added test
• Verify building a bundle with the fix solves https://github.com/gaearon/react-udv-bug/ repro

[react-sizebot]

Comparing: ed69815...df5ef86

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.84 kB	6.84 kB	=	1.88 kB	1.88 kB
oss-stable/react-dom/cjs/react-dom-client.production.js	+0.01%	612.81 kB	612.88 kB	=	108.29 kB	108.30 kB
oss-experimental/react-dom/cjs/react-dom.production.js	=	6.84 kB	6.84 kB	=	1.88 kB	1.88 kB
oss-experimental/react-dom/cjs/react-dom-client.production.js	=	678.75 kB	678.81 kB	=	119.25 kB	119.26 kB
facebook-www/ReactDOM-prod.classic.js	=	698.14 kB	698.20 kB	=	122.65 kB	122.65 kB
facebook-www/ReactDOM-prod.modern.js	=	688.45 kB	688.52 kB	=	121.02 kB	121.03 kB

Significant size changes

Includes any change greater than 0.2%:

(No significant changes)

Generated by 🚫 dangerJS against df5ef86

[acdlite]

Nice! Is it a good or a bad thing that there was already a TODO that (sorta) described the issue 😆

Discussed out-of-band, writing here for posterity:

The TODO I think is still correct, we should generalize that special-error-to-unwind-the-stack trick thing that we use for selective hydration. The main benefit is that if you're mid render it can restart immediately instead of burning cycles on a work-in-progress render that will inevitably get thrown out regardless. Leaving for a future PR in case we were to accidentally introduce a new bug in the progress.