Scanner Microservice - Githubissues

Scanning for files and processing images requires a lot of CPU (open file, parse metadata, extract illustrations, compute blurhash, etc...)

There should be a microservice dedicated to this feature:

[x] We can start scan through an endpoint
- [x] By default, scanning considers all libraries
- [x] Scan can be library-specific
[x] We can start a cleaning task through an endpoint
- [x] By default, cleaning considers all libraries
- [x] Cleaning can be library-specific
[x] We can refresh files' metadata task through an endpoint
- [x] Refreshing can be library-specific
- [x] Refreshing can be album-specific
- [x] Refreshing can be release-specific
- [x] Refreshing can be song-specific
- [x] Refreshing can be track-specific
[x] Tasks cannot run in parallel
[x] We should be able to get the status (i.e. the currently running task) through an endpoint
[x] A Swagger should be present

The Server/API should expose routes dedicated to the scanner:

[x] Delete a File
- [x] It should take a query parameter to trigger (or not) a housekeeping task
[x] Add a File
[x] Get all files
[x] Post an illustration
[x] Post a thumbnail
[x] These routes should be protected, and only accessible by the scanner

[x] Find the language to implement the microservice
[x] Investigate whether ffprobe could be a good candidate to replace the music-metadata library

To Do after everything is implemented

[x] Remove all references to scanning-related settings in server
[x] Rename 'md5Checksum' to 'checksum'
[x] Remove the Task module in the server, as it is not needed anymore
[x] Move housekeeping module into its own module
[x] Create a RegistrationService which will be in change of all the high-level un/registration processes
[x] Ensure that we can not run metadata fetching in parallel
[x] Update Front so that it calls/uses the Scanner