feat: Prevent usage of alan database in main

[y0sher]

Description

Alan release is changing the way our database is structured, specifically the Shares structure loading and saving, we discovered the change is not backward compatible, although its not easily indicated, so if some operator decides to downgrade their operator version back to pre-alan code, its going to run normally but we'll have performance because of the corrupt database.

Task

Write a migration to change ConfigLock mechanism in the new version, so once a pre-alan version tried to open it, it will fail because of the ConfigLock and will not run on the new database.