Feat/auto update binary persistence

[rem1niscence]

Description

Currently, when the canopy auto updater downloaded a new binary in a containerized environment such as docker, it was saved in a non-volume path that would be overwritten with the original file on restarts, this meant that everytime the canopy binary was restarted, it would start at an older version, more specifically, the version of the auto updater.

This fix downloads updates to the data-dir folder and prefers to execute the canopy binary from there, if not found, it will use the original one from the auto updater.

Related Issues

Closes: N/A

Changes Made

• Fix bug where restarting canopy containers would revert the new binary version
• Remove unnecessary releaser.Enabled field

Checklist

• I have tested the changes locally and verified they work as intended.
• I have appropriately titled my branch issue-#<issue-number>.
• I have run re-built the web-wallet and/or block explorer (if applicable).
• I have run npm run prettier to format the web-wallet and/or block explorer (if applicable)
• I have updated documentation (if applicable).
• I have included tests for the changes (if applicable).

Additional Notes

[pablocampogo]

Let me test these changes with my latest change in the graduator and add plugins to the mix