Use the PRAGMA user_version to store the database version

The current migrations are using a version number set in a class attribute. But this means that the database is tight to the application version. What happens when one downgrade its Drive version if there was a modification at the database level not handled in the older version?

Instead, the schema version should be set into the database using the PRAGMA user_version.