feat: Migrate to SQLite

[krocheck]

This implements SQLite to replace the JSON file DB currently used.

Existing DB implementations were moved to /Data/Legacy with write functionality removed in order to facilitate migration to the new format for existing installations. The tables used are simple (id, value) string rows with id flagged a UNIQUE.

This does include a DB version increment from v4 to v5, and this was done to simplify conditions during the migration and ensure import functionality remained untouched. Part of the v4tov5 upgrade is to move controls from the main table into a dedicated controls table. Also, it migrates the separate, legacy clouddb into a cloud table.

Upon startup, the driver ...

1. Attempts to start without create ability. If that fails ...
2. It checks the filesystem for a legacy DB file

• If found, the Legacy driver is loaded, a DB is created, and all data is "as-is" moved to the main SQLite table
• If not found ...

3. It creates a new DB and loads the defaults

TODOs

• Bolster error handling, including startup (attempt to recover backup)
• Deal with types better
• Fix tests
• Test, test, test

Initial testing showed successful OOB startup and migration from a v4 config of relatively small size/scope.