increase constant time test timeout allowing slow runners to complete [skip ci]

[baentsch]

This should allow constant-time testing to pass despite some algorithms being very slow (we won't name them :).

• Does this PR change the input/output behaviour of a cryptographic algorithm (i.e., does it change known answer test values)? (If so, a version bump will be required from x.y.z to x.(y+1).0.)
• Does this PR change the the list of algorithms available -- either adding, removing, or renaming? (If so, PRs in OQS-OpenSSL, OQS-BoringSSL, and OQS-OpenSSH will also be required by the time this is merged.)

[baentsch]

@dstebila - this change was premature, sorry: The no_output_timeout only works on run, not jobs, so please revert this on main. We also already have a 1h timeout, so I now really don't understand last week's test error. Ideas welcome and sorry for writing this correction twice (but it's not here any more....).

[dstebila]

@dstebila - this change was premature, sorry: The no_output_timeout only works on run, not jobs, so please revert this on main. We also already have a 1h timeout, so I now really don't understand last week's test error. Ideas welcome and sorry for writing this correction twice (but it's not here any more....).

Okay, I've pushed a revert directly in commit 65f090d. If this failure persists, we could disable the constant time tests for McEliece on the job and see if that solves it.