fix(tests): prevent flaky dismiss in PointerEvent timestamp test

[mironovsergey]

Description

Fixes a flaky test in the Number options suite where the sheet was occasionally dismissed during a snap-back gesture.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• Test update

Changes Made

• Overrode timeStamp in the PointerEvent mock (jest.setup.js) to use performance.now() from Jest's faked clock instead of jsdom's internal real clock

Root Cause

The custom PointerEvent mock extends MouseEvent, whose constructor sets timeStamp via jsdom's own internal performance reference - bypassing Jest's faked clock. When two events are created in the same synchronous block, their real timestamps can differ by a few microseconds (e.g. dt = 0.001 ms). VelocityTracker then computes:

velocity = 30px / 0.001ms = 30,000,000 px/s

Far above the dismiss threshold → sheet closes when it should snap back. The failure was intermittent because it depended on CPU load at the moment of event construction.

Testing

• New and existing unit tests pass locally (npm test)

[github-actions]

🎉 Thanks for opening your first pull request! We're excited to review your contribution to Bootstrap Sheet.

Please make sure:

• Your code follows our contribution guidelines
• All tests pass (npm test)
• Your code is properly formatted (npm run format)
• You've updated documentation if needed

A maintainer will review your PR as soon as possible. Feel free to ask questions if you need help!