*-boot-tpl: Increase timeout for overlay deployment
To make the test files available to the DUT, LAVA downloads and packages them in a tarball which gets sent to the DUT and unpacked there.
In the group-apparmor-tpl.yaml case the generated overlay is quite big, ~150MB,
and the time needed for the DUT to download and install it is now triggering
the default connection timeout, which is set to 2 minutes.
https://lava.collabora.co.uk/static/docs/v2/timeouts.html#job-timeouts
This results in several INCOMPLETE entries in reports like in the v2019pre/20190502.0 one.
In particular, this is the status of the AppArmor jobs:
- imx6 minimal image fails connecting
- imx6 internal target image fails connecting
- imx6 internal minimal image fails untarring
- minnowboard minimal image fails untarring
- minnowboard target image fails untarring
- r-car minimal image fails untarring
- qemu basesdk image works fine
- qemu sdk image works fine
The main culprit for the size of the overlay is the apparmor-gstreamer1-0
testcase which contains a few relatively large videos. Since LAVA also packs
the .git folder, the amount of bytes consumed by the videos is doubled by the
presence of their git blobs, and the total weight of the testcase is around
100MB alone.
To work around the issue, increase the timeout specifically for the connection matching the overlay download and unpack operation.