Improve checks on DB update

Currently, any update to the database is checked by a specific workflow in GHA. In this check, we confirm that what we store in the local db matches what's stored on the server. I would like these checks to be more exhaustive, for instance:

• Ensure that runs before the new changes are unaffected
• Ensure no invalid values (nans, <0, etc.)
• Ensure the number of entries makes sense
• Ensure no overlap between min/max run
• etc.

Some of these are not trivial, but it would improve our confidence in the database.

Locate the GitHub Actions workflow that checks whether local database updates match the server, then read how its current checks are implemented. Define the expected validation for unaffected prior runs, invalid values, entry counts, and overlapping min/max runs; done means the workflow catches these inconsistencies without rejecting valid updates.