bug: scoped: true / SSR components incorrectly resolve <slot /> during first render

[johnjenkins]

Prerequisites

• I have read the Contributing Guidelines.
• I agree to follow the Code of Conduct.
• I have searched for existing issues that already report this problem, without success.

Stencil Version

latest

Current Behavior

When hydrating scoped: true via SSR, Stencil's vdom-render incorrectly re-renders / does not resolve slot nodes.
This results in incorrect ordering as nodes are remove / re-inserted

Expected Behavior

Nodes in correct order. No extra re-renders

System Info

No response

Steps to Reproduce

Open https://stackblitz.com/edit/stencil-start-ydmeww :

npm run build && npm run express

In the preview window, click on 'non-shadow-multi-slots'.

Notice nodes are in the incorrect order.

Code Reproduction URL

https://stackblitz.com/edit/stencil-start-ydmeww

Additional Information

when re-writing client-hydrate I didn't take into account some new resolving heuristics that were more-recently added to vdom-render.
*edit ... this pattern was completely broken in previous Stencil versions so not a regression

Fix in-bound