Allow tox func tests suite to run in parallel
- append PID to lighty controller log file
This avoids parsing the file of another controller instance.
- increase various timeout limits
- rework tox "depends" parameters used to artificially create a sequel
in parallel mode.
tox -p auto strategy is only based on CPU core numbers and not memory
nor any other parameter. This is not optimal since it can cause other
resources starvation issues in the gate (but not locally).
The new configuration proposed here chains in parallel:
* PCE tests first then 1.2.1 device tests
* 7.1 device tests first then 2.2.1 device tests
This way, only 2 controller instances can be run simultaneously, what
prevents resources from starvation in the gate.
JIRA: TRNSPRTPCE-482
Signed-off-by: Guillaume Lambert <guillaume.lambert@orange.com>
Change-Id: I3a0a66a45a8e170b4554c9de769e1e65b96d224f