mover in cfg and replot enhancements

[tydeno]

This PR focusses on bringing PlotoMover into the PlotoSpawnerConfig.json aswell and make it startable upon launch. Until now, it was necessary to start another PowerShell Session to fire up PlotoMover. Alongside that, it now also supports MountPoints and Network drives! It also brings some new capabilities within the replot mechanism.

Added

• Support MountPoints as OutDrives; Ploto now support the use of MountPoints as outdrives and final drives for mover.
• Support of Network Drives as OutDrives; Ploto now support the use of Network drives as outdrives and final drives for mover
• "ReplotPlotsOlderThan": "20.6.2021 in config parameter. Allows you to define which plots shall be replotted and which not by specifying a date as seen above. This is a mandatory param if you want to replot, as its the only way to determine which plots shall be replotted
• Replot mechanism now picks those drives that have final plots on it for replotting. If there is no drive that has plots to replot, its chooses the best suited OutDrive by free space. If there is none, it aborts.
• Mover is now able to handle several final drives. If there are more than 1 final drives, it picks the one that has no BITS Transfers in progress. If there are non with BITS Transfer in progress, it selects the one with the most available space.

Changed

• PlotoMover cannot be started anymore with params. It uses definable Drives and Paths in config. closes #98
• Changed some outputs to proper meaning and source (function)
• Mover now solely relies on BITS to transfer plots
• Mover now transfer plots async and waits 30 minutes between each move of a plot
• mover ignores plotsolderthan to be moved if replot enabled
• reduced sleep of Watchdog intervall to check for jobs to 1 minute instead of 5

Fixed

• An issue where -p and -f were not ommitted correctly. closes #93
• A couple of potential bugs