Fix disappearing content during interaction

[gbalint]

Problem:
See #5834

There is a way to reproduce this bug without the sample store, just resize the pink rectangle in this project: https://utopia.pizza/project/d8bb2af5

The bug happens in the following situation:

• there is a component (Container in the example) which has a prop coming from an object spread parameter of the component
• this prop specifies the rendered root component/element (in the example the default value is 'div')
• this component has children, and when you interact (e.g. resize) with one of its children, those siblings which are components are not visible during the interaction (MyComp in the example)

You need all of this to reproduce the issue.

• If the sibling is not a component, it is rendered perfectly
• If the prop from the object spread is not used directly but assigned to a local variable, then everything works perfectly.

The faulty behavior is a result of 2 bugs:

1. The component is parsed as ARBITRARY_JS_BLOCK and not as UTOPIA_JSX_COMPONENT. Because of this the Container component is unmounted and remounted at the beginning of the interaction. It is parsed as a js block, because we only allow parsing as a component when the jsx name is known, and the props from the object spread are not included in the known names in the check.
2. ComponentRendererComponent is buggy, and loses its buildResult cached value when a component is remounted and shouldUpdate() is false. This happens because buildResult is a ref initialized with null and it is only filled with the proper value when shouldUpdate() is true.

Fix:

1. I don't think the parser should check if a jsx name is known. When the syntax is clearly jsx, we should parse that as a jsx component. When the jsx name is not known, we will see the proper runtime exception.
   However, fully removing this condition causes problems, because it allows the function below to be parsed as component:

function wrappedComponent(Component) => {
  return <Component />
}

If we parse this as a component our runtime fails to execute it. I think this is a deeper parser issue, and it seems it is mostly pure luck that we parse this as arbitrary block (just because it thinks Component is not known).
I did not dive deeper and just added properties exposed by the params to the list of known names, but I think this problem worth a more detailed investigation. What makes a component a component besides it being a function and returning a jsx?

2. Update the buildResult ref in ComponentRendererComponent even if shouldUpdate is false when its value is 'null'

Manual Tests:
I hereby swear that:

• I opened a hydrogen project and it loaded
• I could navigate to various routes in Preview mode

Fixes #5834

[github-actions]

Try me

[relativeci]

#13427 Bundle Size — 62.63MiB (~+0.01%).

de69956(current) vs 6339ece master#13424(baseline)

Warning

Bundle contains 70 duplicate packages – View duplicate packages

Bundle metrics   2 changes 1 regression

	Current #13427	Baseline #13424
Initial JS	45.7MiB(~+0.01%)	45.7MiB
Initial CSS	0B	0B
Cache Invalidation	22%	26.45%
Chunks	31	31
Assets	34	34
Modules	4374	4374
Duplicate Modules	523	523
Duplicate Code	31.69%	31.69%
Packages	469	469
Duplicate Packages	70	70

Bundle size by type   2 changes 1 regression 1 improvement

	Current #13427	Baseline #13424
JS	62.62MiB (~+0.01%)	62.62MiB
HTML	11.16KiB (-0.33%)	11.2KiB

---

Bundle analysis report Branch fix/remounted-component-renderin... Project dashboard