Use embedded requirements.txt to initialize work env

I've been experimenting on a mechanism to define the list of Python packages needed in the tasks runtime environment.

For the moment it's a very rough prototype, and there are missing features

• add way to override the requirements
• define where the main version of the requirements.txt should be

We should also consider that we will have to migrate to conda.

See also #3 (closed)