Clearing react-router errors requires an extra interaction

[Rheeseyb]

With the removal of the console proxy, and the restoration of the react-router specific error handling (for clearing the canvas after an internal error boundary is triggered) in #5682, the canvas now requires an extra interaction (e.g. scrolling or making another change to the code file, or even saving the code file) before the canvas reset is actually applied (check the video linked in that PR).

After a short investigation I narrowed this down to being caused by the way we update the mount count at the very end of the dispatch (via a mutation)

utopia/editor/src/components/editor/store/dispatch.tsx

Lines 730 to 735 in f53d182

	if (filesChanged.length > 0) {
	finalStoreV1Final.unpatchedEditor = reactRouterErrorTriggeredReset(
	finalStoreV1Final.unpatchedEditor,
	reactRouterErrorPreviouslyLogged,
	)
	}

, and learned the following things:

• Updating the mount count by clicking the reset canvas button in the toolbar still correctly causes the canvas to re-render
• If we update both the patched and unpatched editor states with the new mount count in the above code then the error boundary persists even after further interactions
• The mount count is definitely updated after the error is shown, but the updated value isn't read when pickUiJsxCanvasProps is called (hence why the canvas doesn't actually reset)