Added timeout of async operations to integration test setup/teardown

[ghost]

pull request addressing the issue #3482
Had a look at the causes of the 6h pipeline runs (such as this) - appeared to be async operations in the test cleanup procedure. This change adds timeout to the setup and cleanup of the integration tests.

Is it known why the operations were getting stuck? If not - could more logging be added to look into this problem further?

[eukreign]

@femtosecondlaser thanks for this PR!

the tests don't seem to be passing... also, where does TIMEOUT get set?

i think we always want all tests to have a timeout, there should be some default timeout set (how about 30 seconds)?

[eukreign]

TIMEOUT should be set to a default value somewhere and we always want the timeout enabled, unless you can think of a reason a test might not want to have a timeout?

[coveralls]

Coverage decreased (-0.05%) to 69.636% when pulling e4777f9 on FemtosecondLaser:integration_test_setup_cleanup_timeouts into 3508f56 on lbryio:master.

[ghost]

TIMEOUT should be set to a default value somewhere and we always want the timeout enabled, unless you can think of a reason a test might not want to have a timeout?

TIMEOUT is set to 120 sec here. It has been there for timing out async operations in the main body of the tests. I extended the usage for startup and cleanup parts of the tests.
Timeout gets disabled for some tests here. The removal of conditional set up of timeout makes those tests unhappy.

[ghost]

@eukreign
I suspect the tests are failing for reasons unrelated to this change.
The latest run failed while building for mac. All the tests passed.
I don't have an option to re-run the pipe, could you do that please.