Bug: Inconsistent Range Input Behavior in Time Travel Feature of TreeView between Create React App (CRA) and Next.js

When using the Time Travel feature of the ``, I have observed different behaviors with the range input in Create React App (CRA) and Next.js. Specifically, when I hit the Time Travel button, the value of the range input's indicator is set to its maximum value for CRA, while it is set at its middle position for Next.js.

Lexical version: 0.11.1

## Steps To Reproduce

1. Run an application built with `` in CRA and Next.js
2. Provide some texts in the ``
3. Hit the `Time Travel`
4. Observe the range input's indicator positioned.

## The current behavior
In CRA, when using the Time Travel feature, the range input's indicator is consistently positioned at its maximum value. However, in Next.js, the indicator is consistently set at its middle position.

## The expected behavior
In both CRA and Next.js, the range input's indicator should maintain consistent behavior when using the Time Travel feature of the ``. The default position of the indicator should align with wherever the value of the range input that is supposed to be.

Reproduce the Time Travel behavior with the TreeView and ContentEditable components in both Create React App and Next.js. Inspect the TreeView time-travel range input and compare its value and indicator position in each setup; done means the indicator behaves consistently in both environments.

Written by the indexing model from the issue text.