* Rename setenv to printenv
This is done for anod internally and seems much more clear than `setenv` (given that it doesn't actually set anything).
Options to print the environment for the installer are also modified to `--printenv` which is consistent with internal anod.
Clean up the output of install - specifically, have it give a correct set of commands to add to the .profile.
Finally, use the better (safer) syntax for the eval, so the user can get used to it.
Support pre-commit checks used in AdaCore/e3-core
These are a good example of best style practices for python projects. Adding the associated badges to the README (even though it needs to be rewritten) so the commit is complete and consistent.
Documentation of how to set up and run the checks is in CONTRIBUTING.md
Master `anod` script that dispatches to subscripts for action.
Add `paths` module, which group common path-related constants.
Improve anod-devel-setup to use e3 and logging.
