Use section timeline context for roving map QSO origins

[rwjblue]

Map lines and distance calculations were using the operation's final location, which made roving logs look like every contact came from the last stop.

This changes map rendering to follow the same section timeline model used elsewhere: we derive per-QSO origin context from start/break snapshots and render each contact from the location active at log time. The same shared timeline helper is now used by ADIF traversal as well, so segment behavior stays aligned instead of being reimplemented in separate places.

This also updates @ham2k/lib-qson-tools to 1.3.1 for the shared section-context helpers and CommonJS package export used by the current Jest setup.

Test plan

• Create or load a multi-stop roving operation with start/break events and verify map lines originate from the location active when each QSO was logged.
• Verify single-grid operations render map lines and distances as before.
• Export ADIF for a segmented operation and confirm segment-based refs/grid behavior remains consistent.

Local validation

• npm test -- --runInBand --watchman=false src/tools/qsonToADIF.spec.js
• npx eslint src/tools/qsonToADIF.js src/screens/OperationBadgeScreen/OperationBadgeScreen.jsx src/screens/OperationScreens/OpMapTab/OpMapTab.jsx src/screens/OperationScreens/OpMapTab/components/MapWithQSOs.jsx src/screens/OperationScreens/OpMapTab/components/MapboxMapWithQSOs.jsx
• npm test -- --runInBand --watchman=false
• clean temp install with Node 22: npm ci && npm test -- --ci

Screenshots

Single point

Multiple points

[rwjblue]

I tried to run npm run lint, but it doesn't seem to be working at the moment (#205 starts working on that). I'll run prettier at least to make sure that formatting of the new files is right.