Revise Repository to Account for Multiple New Functionalities

[maxachis]

This repository is quickly outgrowing its initial role as simply a repository for prod to dev migrations. Now with backup management under development, and with the role of the code changing in v2, now's the time to revise the structure of the repository, eliminate redundant code

• Change name to something more acceptable
• Restructure the repository so that different functionalities exist in different sub-directories (as opposed to now, where the root directory contains migration scripts, and a subdirectory contains backup management scripts
• Some code is redundant and should be combined and edited
• Revise automation jobs accordingly and ensure they still function with these adjustments.