[Fizz] Clean up the replay nodes if we're already rendered past an element

[sebmarkbage]

Follow up to #27513. There's two issues here.

First, we didn't restore the ReplaySet when calling renderNode() so it was not safe to invoke since future siblings might observe the mutated replay. This could skip replays which covered up errors.

Second, this was covering up that we weren't properly cleaning up the replay nodes when we were able to render through one node and then mutated the .node on the task but then suspended deeper.

I don't love the solution from #27513 in general because it feels hacky to compare the mutated node. It should probably be structured different. There's also another case that's basically the same case which has neither of these fixes in it. It's probably a bug too but haven't been able to repro yet:

react/packages/react-server/src/ReactFizzServer.js

Lines 3612 to 3613 in a947eba

	// Suspend
	throw x;

[react-sizebot]

Comparing: a947eba...917c674

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	=	530.57 kB	530.57 kB	=	93.67 kB	93.67 kB
oss-experimental/react-dom/cjs/react-dom.production.js	=	6.69 kB	6.69 kB	+0.05%	1.83 kB	1.83 kB
oss-experimental/react-dom/cjs/react-dom-client.production.js	=	651.66 kB	651.66 kB	=	114.78 kB	114.78 kB
facebook-www/ReactDOM-prod.classic.js	=	674.81 kB	674.81 kB	=	118.78 kB	118.78 kB
facebook-www/ReactDOM-prod.modern.js	=	665.30 kB	665.30 kB	=	117.19 kB	117.19 kB

Significant size changes

Includes any change greater than 0.2%:

(No significant changes)

Generated by 🚫 dangerJS against 917c674