Add new explicit migration command

[DL6ER]

What does this implement/fix?

pihole-FTL migrate v6 is intentionally not included in the help output as it is solely meant to be used internally by the installer script once from v5 -> v6

Related to pi-hole/pi-hole#5830

Related issue or feature (if applicable): N/A

Pull request in docs with documentation (if applicable): N/A

---

By submitting this pull request, I confirm the following:

1. I have read and understood the contributors guide, as well as this entire template. I understand which branch to base my commits and Pull Requests against.
2. I have commented my proposed changes within the code.
3. I am willing to help maintain this change if there are issues with it later.
4. It is compatible with the EUPL 1.2 license
5. I have squashed any insignificant commits. (git rebase)

Checklist:

• The code change is tested and works locally.
• I based my code and PRs against the repositories developmental branch.
• I signed off all commits. Pi-hole enforces the DCO for all contributions
• I signed all my commits. Pi-hole requires signatures to verify authorship
• I have read the above and my PR is ready for review.

[pralor-bot]

This pull request has been mentioned on Pi-hole Userspace. There might be relevant details there:

https://discourse.pi-hole.net/t/broken-installation/74638/25

[yubiuser]

As far as I can see no functional changes but only putting code into new functions

[DL6ER]

Tested on two virtual machines to do what it should. The latest commit ensures we log the migration process to the user so they can quickly review if everything went the way they'd expect it to.

[DL6ER]

The most recent commit adds code to ensure a broken (or too new) database is not used when we know that all the SQL statements against it will fail anyway

[DL6ER]

Rebased on latest development

[yubiuser]

Maybe I was too fast. Importing v5 backups results in SQL database locked errors. It does not happen every time, so maybe it's a race collission

2025-01-08 12:12:15.997 CET [147804/T148076] INFO: import_json_table(client_by_group.json): JSON array contains 0 entries
2025-01-08 12:12:16.017 CET [147804/T148076] INFO: import_json_table(domainlist_by_group.json): JSON array contains 64 entries
2025-01-08 12:12:16.036 CET [147804/T148076] INFO: import_json_table(group.json): JSON array contains 3 entries
2025-01-08 12:12:16.050 CET [147804/T147886] ERROR: SQLite3: database is locked in "SELECT value FROM info WHERE property = 'updated';" (5)
2025-01-08 12:12:16.058 CET [147804/T148076] INFO: import_json_table(whitelist.exact.json): JSON array contains 26 entries
2025-01-08 12:12:16.083 CET [147804/T148076] INFO: import_json_table(whitelist.regex.json): JSON array contains 3 entries

2025-01-08 12:13:43.029 CET [147804/T148365] INFO: import_json_table(blacklist.regex.json): JSON array contains 27 entries
2025-01-08 12:13:43.048 CET [147804/T148365] INFO: import_json_table(client.json): JSON array contains 0 entries
2025-01-08 12:13:43.069 CET [147804/T148365] INFO: import_json_table(client_by_group.json): JSON array contains 0 entries
2025-01-08 12:13:43.082 CET [147804/T148365] ERROR: Unable to commit transaction: database is locked
2025-01-08 12:13:43.088 CET [147804/T148365] INFO: import_json_table(domainlist_by_group.json): JSON array contains 64 entries
2025-01-08 12:13:43.107 CET [147804/T148365] INFO: import_json_table(group.json): JSON array contains 3 entries
2025-01-08 12:13:43.129 CET [147804/T148365] INFO: import_json_table(whitelist.exact.json): JSON array contains 26 entries
2025-01-08 12:13:43.153 CET [147804/T148365] INFO: import_json_table(whitelist.regex.json): JSON array contains 3 entries