increase the timeout for window platform to avoid flaky test

[iuhilnehc-ynos]

A flaky test about launch_testing_examples\check_multiple_nodes_launch_test.py is always reported while running CI.

After comparing the success and failure cases between https://ci.ros2.org/job/ci_windows/18721/consoleFull and https://ci.ros2.org/job/ci_windows/18738/consoleFull, I suspect that the timeout of waiting on the Window platform might not be enough.

Successful log in https://ci.ros2.org/job/ci_windows/18721/consoleFull,

01:22:55 launch_testing_examples\check_multiple_nodes_launch_test.py RR.          [ 22%]

Failure log in https://ci.ros2.org/job/ci_windows/18738/consoleFull.

23:58:21 launch_testing_examples\check_multiple_nodes_launch_test.py RRF          [ 22%]

We can find two re-test actions even in the successful log. (RR.)

[iuhilnehc-ynos]

First time to run CI on Window. (1/10)

• Windows

[iuhilnehc-ynos]

ran CI with wrong value --package-select for CI_TEST_ARGS before, which should be --packages-select.
rerun CI (2/10),

• Windows

22:29:56 launch_testing_examples\check_multiple_nodes_launch_test.py .            [ 22%]
no more `re-test` action

rerun CI (3/10),

• Windows

rerun CI (4/10),

• Windows

rerun CI (5/10),

• Windows

rerun CI (6/10),

• Windows

In order to not occupy the CI resource, I'll rerun a full CI later.

[iuhilnehc-ynos]

CI:

• Linux
• Linux-aarch64
• Windows

[clalancette]

I'm going to go ahead and merge this one, since it is low-risk and seems to be helping. We can always do another follow-up if this isn't enough.