the progress bar can now works when running in the background

the GUI, when calling the script, mixes up separators if there is more
than one underscore.

document the manual installation using docstrings

CV generation is very long due to the conversion of the IV and DV from
v2.0 to 1.3 .. A progress bar is mandatory to inform the user that
something is happening in the background

V2 uses a different syntax file to alter the Priortiies/Offset of tasks

Attempting to introduce per-deployment target env vars
defined in the AADL files that describe the targets.

...to work with TASTE v2

- in case of V2: do the md5 on the v2 version, not on v1.3 converted IV
- concurrency view generator: support v2