Arvid@pytest timeout

Context

Depends on !3870 (merged).

After !3870 (merged), pytest no longer show stdout unless they fail. However, if the test is stuck, the gitlab job timeout (typically at 4h) will be reached. At that point, the job is terminated and pytest will not show any output at all. In this MR, we set a per-test case timeout of 30 minutes (currently, the slowest test case takes 3 minutes to finish, so I multiplied by ten).

Pytest has no option for global timeouts.

Manually testing the MR

Check the CI.

You can set the timeout to something low, like 10s and see how that looks. Here's an example: https://gitlab.com/nomadic-labs/tezos/-/pipelines/414835692

Checklist

• Document the interface of any function added or modified (see the coding guidelines)
• Document any change to the user interface, including configuration parameters (see node configuration)
• Provide automatic testing (see the testing guide).
• For new features and bug fixes, add an item in the appropriate changelog (docs/protocols/alpha.rst for the protocol and the environment, the Development Version section of CHANGES.md for everything else).
• Select suitable reviewers using the Reviewers field below.
• Select as Assignee the next person who should take action on that MR