fix(render): remove overlapping nodes + old connected nodes

[aralroca]

Fixes #686

This PR fixes bugs encountered with different reactive parts sharing nodes of the same element.

Example:

Signal 1 -> when true -> fragment -> Signal 2 -> when true -> render
                                                          -> render sibling

In this scenario, when Signal 2 changes, it updates the local refs of this reactivity part but does not communicate with Signal 1 to update this ref (so hard to do this...). So after this PR, when Signal 1 needs to update the nodes without this ref, it cleans the overlapped nodes first to do the job correctly. Then, instead of removing the referenced nodes, it removes the real ones, doing nextSibling until the last ref.

For me, the ideal solution would be not to depend on these local references. But, at least, with this solution we avoid doing a reconciler for it or adding markers to the HTML. 😅

Caution

Bad part: It increases 110 bytes the client code, (still 3kb but rounded is 4kb). At least in a previous PR I reduce 26 bytes this code, so the total new bytes in the next release will be +84 bytes.

[pkg-pr-new]

Open in Stackblitz

brisa-adapter-vercel

npm i https://pkg.pr.new/brisa-build/brisa/brisa-adapter-vercel@702

brisa

npm i https://pkg.pr.new/brisa-build/brisa@702

brisa-pandacss

npm i https://pkg.pr.new/brisa-build/brisa/brisa-pandacss@702

brisa-tailwindcss

npm i https://pkg.pr.new/brisa-build/brisa/brisa-tailwindcss@702

create-brisa

npm i https://pkg.pr.new/brisa-build/brisa/create-brisa@702

www

npm i https://pkg.pr.new/brisa-build/brisa/www@702

commit: 55a6a48

[aralroca]

We can golfing bytes in future PRs to keep Web Components to 3kb