[FLINK-39413][runtime] Speed up TaskExecutorSubmissionTest#testRemotePartitionNotFound by configuring partition request timeout

[mukul-8]

What is the purpose of the change

testRemotePartitionNotFound takes ~20s because NETWORK_PARTITION_REQUEST_TIMEOUT defaults to 10s,
causing the listener to miss the first check window and wait for the second (~20s). The backoff mechanism
is also never exercised since the default timeout (10,000ms) immediately exceeds 2 * maxBackoff (400ms).

Brief change log

• Set NETWORK_PARTITION_REQUEST_TIMEOUT to 100ms in the test configuration

Verifying this change

Ran this test locally with @RepeatedTest 200 times each run takes less than 1 sec

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

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)

Generated-by: Kiro CLI (Amazon Q based AI agent)

[flinkbot]

CI report:

• e73e4d6 Azure: FAILURE

Bot commands

The @flinkbot bot supports the following commands:

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

[mukul-8]

@flinkbot run azure