fix: use capture timestamps for alert detections

[Stava-Java]

Closes #146

Changes

Detection responses now parse recorded_at. The sequence service sorts detections by that capture timestamp. The player uses the same timestamp for slider positions, endpoint labels & the selected value label. Database created_at values no longer control playback order.

The regression test supplies two detections whose database & capture timestamps sort in opposite directions. It expects the capture-time order.

Verification

• Vitest: 13 files, 113 tests passed
• TypeScript project build
• Prettier check on the 3 changed files
• ESLint on the 3 changed files

[vercel]

@Stava-Java is attempting to deploy a commit to the Pyronear Team on Vercel.

A member of the Team first needs to authorize it.

[fe51]

Hi @Stava-Java nice to meet you and thank you for opening the PR !
Thanks to it, sppoted a bug, API side, issue has been open !
pyronear/pyro-api#675

[MateoLostanlen]

On the API side, pyronear/pyro-api#687 aligns sequence started_at with the recorded_at of their first detection. This PR is complementary: the player shows capture time, the API makes it consistent with the sequence start. Both can be merged in any order.