Lad performance fixups

[OSPFNeighbour]

This pull request makes significant improvements to the filtering, performance, and user experience of the main tasking page. The most notable changes include switching to Set-based filtering for better performance and correctness, introducing efficient marker batching to reduce UI lag during burst updates, refining the initial map loading and fit behavior, and improving the way relative time labels are updated for assets.

Filtering and Performance Improvements:

• Replaced array-based .includes() filters with Set-based lookups for jobs and teams, improving performance and reliability, especially with large datasets. This affects filters for HQs, sectors, statuses, incident types, and pinned items. (src/pages/tasking/main.js) [1] [2] [3] [4] [5] [6] [7]
• Updated Knockout computed observables to use a more efficient rate limiting method (notifyWhenChangesStop) for reduced unnecessary UI updates. (src/pages/tasking/main.js)

Map and Marker Handling Enhancements:

• Introduced a marker batching system using requestAnimationFrame to schedule add/remove operations for job and asset markers, significantly reducing layout thrash and improving responsiveness during bulk updates. (src/pages/tasking/main.js) [1] [2] [3] [4] [5] [6]
• Improved initial map fit logic: now waits for all data to load, handles user interaction gracefully, retries if needed, and falls back to calculating bounds from raw data if markers are not yet attached. Also added a loading overlay that hides once loading is complete. (src/pages/tasking/main.js) [1] [2]

Asset Model and Relative Time Updates:

• Refactored the Asset model to accept a shared relative update tick observable, ensuring all assets update their relative time labels in sync every 30 seconds, rather than each asset managing its own timer. (src/pages/tasking/models/Asset.js, src/pages/tasking/main.js) [1] [2] [3] [4] [5]

User Experience Improvements:

• Enhanced the job timeline modal to start and stop auto-refreshing only when the modal is shown or hidden, preventing unnecessary background updates. (src/pages/tasking/main.js)

These changes collectively make the tasking page more performant, responsive, and user-friendly, especially in scenarios with large numbers of jobs, teams, and assets.