Persist Lap Data to Topic Store

Description

When a new lap is started, the backend should record it under an incrementing topic path (e.g. timers/lap/1, timers/lap/2) with the epoch microsecond timestamp as the value. This makes lap data available to the broader Argos telemetry pipeline alongside other topic data.

Acceptance Criteria

• Each new lap creates a new entry under timers/lap/<n> where n increments per lap
• Value stored is epoch microsecond timestamp of lap start
• Lap number resets or persists across sessions (clarify during implementation)

Proposed Solution

Just add service layer logic for doing this, simply a function that allows for auto-incrementing a new lap time to the database. Auto increment by querying for the sorted dataTypeName (for the current runID). You could also explore only doing that query on startup and then auto incrementing in memory, to avoid expensive queries.

Add lap creation logic in scylla-server/src/. Reference existing topic/value insertion patterns. Test using Postman, add tests to the relevant test file.

Mocks

No response