fix: LEAP-1931: Correct frame offset calculation in Timeline

[Gondragos]

Reason for change:

The frame offset calculation in the Timeline component did not account for currentOffsetX, which led to improper determination of valid offset ranges. This caused inconsistent behavior in seeking the right video frame for displaying.

Before:

Solution:

The check for frame offsets was adjusted to include currentOffsetX. This ensures accurate calculations and resolves the inconsistency.

After:

Rollout strategy:

This code will be rolled out as part of the next release and does not require feature flags or environment variables.

Testing:

• Manually tested.

Risks:

This change modifies a critical calculation in the Timeline. There is a minor risk of unforeseen edge cases that might have been missed.

Reviewer Notes:

From the code perspective offset contains the value of the current mouse x coordinate related to the timeline itself plus currentOffsetX which is basically scrollLeft. Although it's unclear why that method was called getMouseToFrame, it's pretty clear that the next condition was working fine only when the timeline's frame is placed at the left edge.

[netlify]

✅ Deploy Preview for label-studio-docs-new-theme canceled.

Name	Link
🔨 Latest commit	b566a5f
🔍 Latest deploy log	https://app.netlify.com/sites/label-studio-docs-new-theme/deploys/67dbe85205a93e0008a0e26e

[netlify]

✅ Deploy Preview for heartex-docs canceled.

Name	Link
🔨 Latest commit	b566a5f
🔍 Latest deploy log	https://app.netlify.com/sites/heartex-docs/deploys/67dbe852f15fa5000812648a

[Gondragos]

/git merge

Workflow run
Successfully merged: create mode 100644 web/tools/design-tokens-converter/package.json

[MihajloHoma]

/git merge

Workflow run
Successfully merged: 18 files changed, 117 insertions(+), 60 deletions(-)

[MihajloHoma]

/fm sync

Workflow run