Mdbackup

- Implemented *unactions* system for the future restore mode
- Deployed documentation to GitHub Pages: [mdbackup.majorcadevs.com](https://mdbackup.majorcadevs.com/)
- Implemented CI/CD to auto-deploy documentation on dev or master pushes
- Fix S3 without region raises `KeyError` exception
- `xattr` package is only required on non-Linux OSes
- Uploading backups will now keep some folder structure and will only archive folders that were result of a task. This will simplify restore operations in any sense :)

**breaking changes**
- Command arguments has been reworked. Now it has subcommands. Checkout documentation :)

- Added config validations using json schema.
- When uploading to cloud storage, compress and/or encrypt steps are done using actions implementation (avoiding duplicated code).
- Added more tests :)

Breaking changes:
- `compression`, `encrypt` and `storages` are now inside a `cloud` parent element.
- `storages` is called now `providers`.
- `ftp` and `ftps` providers now have `port` setting.
- `sftp` changed the setting from `disableHostKeys` to `enableHostKeys`.
- Action `compress-gzip` is now called `compress-gz`.

New Features

- Added support for `.yaml`/`.yml` config files.
- Improvements and bug fixes on S3 and B2 upload.
- Configuration `-c` option now expects a folder with a config file and tasks.
- File secrets backend will default to `${config_folder}/secrets` as `basePath` instead of fail.
- Implemented actions and tasks.
- Backups will have a *backup manifest* with information about what has been run and what files/folders have been generated from each *task* - useful for a future restoring functionality.

Breaking changes

- Configuration switch `-c` expects folder not a config file.
- Backup logic is now done using *actions* and *tasks* which are defined using `yaml` files inside `${config_folder}/tasks`.

* Fix: backups can fail if the backupPath has any symbolic link in the path
* Fix: S3 creating weird folders
* Fix: FTP/FTPS/SFTP several failures related to create_folder and list_directory
* Fix: uploading backup was creating bad folders
* Fix: `upload-current-only` does not get storages from secret backends

This release comes with a lot of new features listed below :)

- 13 Mikrotik implementation
- 14 Hooks scripts
- 15 FTP, FTPS and SFTP storage providers
- 16 Change implementation of B2 to `b2sdk`
- 18 23 `mdbackup` in a docker image - see https://hub.docker.com/majorcadevs/mdbackup
- 19 Added `StorageClass` setting to S3
- 21 Improve secrets implementation
- 22 Implement retention in storage providers (20)
- 17 Documentation (soon URL to see them online)
- 25 Documentation docker image

This release comes with a bunch of new features and some bug fixes that made the utility more secure, flexible and save to use. That's the list of new features and bug fixes:

Features

- [1] Vault secret backend - store important data (like passwords) in this secret backend and mdbackup will retrieve those secrets for you :)
- [1] File secret backend - a fallback secret backend, secrets are read from the file system directly
- [2] Backblaze integration - new cloud storage provider
- [40207c8a9f242aae3255235adf6b2dd943899bcb] S3-like integration - new cloud storage provider for those S3-like services
- [5] Moved to optional dependencies. Now if you don't use S3 nor Backblaze, those libraries won't get installed. Only install what you need.
- [6] Ability to run some parts of the tool by adding some arguments when invoking it
- [7] Bash scripts can now write debug logs. Just print a line starting with `DEBUG: ` (space included).

Bug fixes

- [c4405732beebe32d604f14efc20d8311bc020403] Handle exceptions when a bash script is running
- [c4405732beebe32d604f14efc20d8311bc020403] Backup of a docker volume doesn't create the backup
- [4] Follow symlinks when uploading backups
- [8] [9] Fix postgresql backups when running with a different user and/or requires a password to be supplied from terminal