fix: skip native Date fast path when local timezone is overridden via setLocalTimeZone (#9678)
* fix: skip native Date fast path when local timezone is overridden via setLocalTimeZone
When setLocalTimeZone is called with a timezone different from the browser's,
the fast paths in getTimeZoneOffset and toAbsolute incorrectly use native Date
(which always reflects the browser timezone) instead of the Intl-based path.
This causes incorrect offset calculations for the overridden timezone.
Skip the native Date fast paths when setLocalTimeZone has been called, falling
back to the correct Intl.DateTimeFormat-based computation.
Fixes #9669
* fix: use before/after comparison in resetLocalTimeZone test to avoid -0 vs 0 issue in UTC CI
* fix: fix lint import ordering and add isLocalTimeZoneOverridden queries tests
- Fix alphabetical import sorting in conversion.ts
- Export isLocalTimeZoneOverridden from public index
- Add isLocalTimeZoneOverridden unit tests in queries.test.js as requested