Rollback 4.4.1 release

What does this MR do and why?

Rollback 4.4.1 as unexpected high-load operation on Backups Migrations,

This release contained migrations that required moving backups to a new directory using a pre-existing helper func FileHelpers.move(), preparing for the multiple backup refactor. This helper function's filesystem operation was a copy-del operation instead of a move operation, causing crafty to take an excessive amount of time to process migrations on post-upgrade boot.

This managed to pass through integration tests as test instances were operating with backups of minimal volume, allowing operations to complete quickly and successfully. However, this is an unfit release for production systems due to the time required for large migrations to complete, for users with backups of a significant size, running on low bandwidth storage mediums, machines would likely not be able to have crafty boot following update as migration time would be unfeasible. Some users may kill instances prematurely causing irreparable database damage.

4.4.2 will contain a patch for this release correcting Helper function. 4.4.1 & 4.4.2 will be reintroduced into master together.

Impact Statement: Release rolled back before docker build completed, saving any docker instances operating w/ watchtower upgrade automation, win build finished but will be overwritten.