Increase the timeout for the docker timeout test.

[stuhood]

See #16855. The timeout is applied only after we have successfully opened an output stream from the process, so the hypothesis with this test is that the process just runs more slowly under docker, and needs longer to get to the point where it can render output.

Fixes #16855.

[ci skip-build-wheels]

[tdyas]

so the hypothesis with this test is that the process just runs more slowly under docker, and needs longer to get to the point where it can render output.

Also, each test is spawning its own cached container since each test instantiates a separate instance of docker::CommandRunner. We could use a shared command runner for the tests to increase performance of the tests at the risk of coupling otherwise unrelated tests together.

[stuhood]

Also, each test is spawning its own cached container since each test instantiates a separate instance of docker::CommandRunner.

That shouldn't impact the performance of the process once we've already attached (should it?), which is when the timeout comes into play.

[tdyas]

That shouldn't impact the performance of the process once we've already attached (should it?), which is when the timeout comes into play.

Ah yeah, probably not then.