[FLINK-31354][tests] Increased timeout for NettyClientServerSslTest to improve test stability

[XComp]

What is the purpose of the change

We see the test occassionally fail due to slow CI machines (see further details in FLINK-31354). Increasing the timeouts should solve the issue.

Brief change log

• Increased the timeouts from 1s to 5s

Verifying this change

This change is a trivial rework / code cleanup without any test coverage.

Does this pull request potentially affect one of the following parts:

• Dependencies (does it add or upgrade a dependency): no
• The public API, i.e., is any changed class annotated with @Public(Evolving): no
• The serializers: no
• The runtime per-record code paths (performance sensitive): no
• Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
• The S3 file system connector: no

Documentation

• Does this pull request introduce a new feature? no
• If yes, how is the feature documented? not applicable

[XComp]

@zentol I guess, increasing the timeout should not cause any problems?! The test usually runs in milliseconds but occasionally runs into the 1000ms limit.

[flinkbot]

CI report:

• 9251a0a Azure: SUCCESS

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot run azure re-run the last Azure build

[dmvk]

The test usually runs in milliseconds but occasionally runs into the 1000ms limit.

Can we simply increase the timeouts to a really high number (~ 1h-ish)?

[XComp]

Yeah, we could do that. It doesn't do much of a difference to the test. The test sets up the Netty context and verifies that timeout config values are forwarded correctly. I changed the test slightly to serve different values rather than relying on the same value to improve the test case

[dmvk]

👍 LGTM, thanks for the update