CI: fix flaky test via extended timeout in vrepl_stress_suite

[shlomi-noach]

Description

Discussion: #8969 (comment)

Gonna create this PR as Draft and run vrepl_stress_suite multiple times to see if this fixes the flakiness. The tests have been stable for months, and recently became flaky. First suspicion is GitHub CI runners getting slower.

Related Issue(s)

#8969 (comment)

Checklist

• "Backport me!" label has been added if this change should be backported
• Tests were added or are not required
• Documentation was added or is not required

[shlomi-noach]

All right, ran the test 10 times and it always passed. this looks good to me, and it seems like GitHub CI just got slower and that we need longer timeouts. I'll look into other onlineddl tests and increase timeouts as needed.

Thanks to @mattlord who identifies the root cause of the failure.

[shlomi-noach]

Ready to review, and not a moment too soon 😛

[github-actions]

Review Checklist

Hello reviewers! 👋 Please follow this checklist when reviewing this Pull Request.

General

• Ensure that the Pull Request has the correct release notes label. release notes none should only be used for PRs that are so trivial that they need not be included.
• If a new flag is being introduced, review whether it is really needed. The flag names should be clear and intuitive (as far as possible), and the flag's help should be descriptive.

Bug fixes

• There should be at least one unit or end-to-end test.
• The Pull Request description should either include a link to an issue that describes the bug OR an actual description of the bug and how to reproduce, along with a description of the fix.

Non-trivial changes

• There should be some code comments as to why things are implemented the way they are.

New/Existing features

• Should be documented, either by modifying the existing documentation or creating new documentation.
• New features should have a link to a feature request issue or an RFC that documents the use cases, corner cases and test cases.

Backward compatibility

• Protobuf changes should be wire-compatible.
• Changes to _vt tables and RPCs need to be backward compatible.
• vtctl command output order should be stable and awk-able.

[mattlord]

❤️