[feat] use configuration files

[unsync]

The goal is to use a config file for excludes/includes, allowing to define custom paths. The default config files are created if they do not exists, with the same defaults as the current script.

Tested on MacOS 11.2

[j-f1]

How would this work if Asimov were to add additional paths to either of these lists in the future?

[unsync]

@j-f1 well, it would not work as it is ^^ you got several way to look at it depending on the direction wanted for this tool :

• you set sane default during inital install, then you got full control over the sentinels
• you add logic in the script that adds the new sentinels wanted by asimov

one could argue that the defaults by asimov do not work in their use case (maybe some wants to backup their node_modules, then reliyng only on defaults is a drawdown).

This PR is mostly a base for discussions, you could imagine several lists (defaults, excludes, overrides, etc)