[react-dom] Batch updates from resize until next frame

[eps1lon]

Resize is closer to scroll events which are already batched during a frame. We previously flushed state updates from resize events when new discrete events came in. Now resize is batched with other continuous events.

We stil flush before the next frame is painted.

[react-sizebot]

Comparing: 1ea46df...2ffe311

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	=	1.83 kB	1.83 kB
oss-stable/react-dom/cjs/react-dom-client.production.js	=	608.16 kB	608.16 kB	=	107.64 kB	107.65 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	=	666.18 kB	666.18 kB	=	117.35 kB	117.35 kB
facebook-www/ReactDOM-prod.classic.js	=	693.31 kB	693.31 kB	=	121.97 kB	121.98 kB
facebook-www/ReactDOM-prod.modern.js	=	683.73 kB	683.73 kB	=	120.36 kB	120.36 kB

Significant size changes

Includes any change greater than 0.2%:

(No significant changes)

Generated by 🚫 dangerJS against 2ffe311

[Samdevelop25]

This PR introduces a small but meaningful performance optimization by batching resize updates until the next animation frame, reducing unnecessary render cycles and improving layout stability during continuous resizing.