Context

The current throttle implementation in src/util/Function.mjs has two issues:

1. Inefficiency: It clears and recreates setTimeout on every call during the cooldown period solely to capture the latest arguments.
2. Fragility: It relies on a strict timing check (Date.now() - lastRanDate) >= delay inside the timeout. If the browser fires the timeout even 1ms early (common jitter), the trailing call is silently dropped.

Objective

Rewrite throttle to use a standard, robust pattern:

1. Leading Edge: Execute immediately if now - lastRun > delay.
2. Trailing Edge: If inside cooldown, store the latestArgs. Schedule a SINGLE timeout for the remaining time if one doesn't exist.
3. Execution: When the timeout fires, execute with latestArgs, update lastRun, and clear the timeout flag.

This ensures ScrollManager (and other components) never lose the final update event, preventing visual desyncs.