chore: consistent nextSibling usage

[trueadm]

We should avoid doing node.nextSibling and instead use the next_sibling(node) function which is slightly faster and avoids deopts.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 4f50b74

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[Rich-Harris]

Actually I tested this locally and it made things slower for me. Going to revert it