sist2-admin should automatically run a full rescan on version mismatch. Add option to run a full mismatch in the UI

[dpieski]

Device Information (please complete the following information):

• Deployment: [Linux, Linux ARM64 or Docker] Docker
• SIST2 Version: [e.g., v2.9.0] 3.2.0

Describe the bug

When I scan after the update to 3.2.0:

2023-08-09 13:34:13 [DEBUG database.c] Opening database /sist2-admin/scan-Litigation-2023-04-27 16:23:22.842104.sist2 (0)
2023-08-09 13:34:13 [FATAL database.c] Sqlite error @ /build/src/database/database.c:167 : (1) table document has no column named version

Expected behavior

I would expect it to make a new database that conforms to the changes.

Actual Behavior

It also crashes the frontend with:

{"stderr": "T0 [2023-08-09 13:33:10] [FATAL database.c] Sqlite error @ /build/src/database/database.c:167 : (1) table document has no column named version\n"}

Additional context

A side-issue: So, I need to make it do a full scan and not an incremental scan in order to create the new db. Since I don't use the thumbnails, I change the "Thumbnail Quality" value to get it to re-scan everything since changing that value triggers a full re-scan. It would be helpful if there was a button on that page that could do a full re-scan.

Also, It could be helpful if breaking changes would also cause a re-scan instead of incremental scan.

[dpieski]

Regarding options to run a full scan instead of incremental:

Or maybe like a check-mark box for like '[] Run full Scan on next Index'

Or a dropdown button like Github has for "Close with comment" | "Close as not planned" so like "Incremental Index Now" | "Full Index Now" defaulting to incremental.