Better handling of issues caused by time traveling (RiskResults) (DEV) #2019

* Change primary key for risk result database to a monotonic ID.
This prevents time travel from breaking "get latest" as we will get the latest by monotonic ID, instead of "calculatedAt".

* We don't need `fallbackToDestructiveMigrationFrom(3)` until we actually upgrade the schema to 3.

* Fix database test (missing monotonicId)

* Catch exceptions during migrations and recreate the table.

* Add check for result size after recreating+insertion.

Co-authored-by: Ralf Gehrer <ralfgehrer@users.noreply.github.com>