CNDB-14023 Adds timeout while waiting for node to be marked down to avoid JUnit test timeouts.

[djatnieks]

What is the issue

CNDB-14023, ForceRepairTest fails sometimes in CI with a JUnit test timeout.

What does this PR fix and why was it fixed

Adds a timeout while waiting for node to be marked down instead of waiting indefinitely and raising a JUnit timeout.

[github-actions]

Checklist before you submit for review

• This PR adheres to the Definition of Done
• Make sure there is a PR in the CNDB project updating the Converged Cassandra version
• Use NoSpamLogger for log lines that may appear frequently in the logs
• Verify test results on Butler
• Test coverage for new/modified code is > 80%
• Proper code formatting
• Proper title for each commit staring with the project-issue number, like CNDB-1234
• Each commit has a meaningful description
• Each commit is not very long and contains related changes
• Renames, moves and reformatting are in distinct commits
• All new files should contain the DataStax copyright header instead of the Apache License one

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[cassci-bot]

❌ Build ds-cassandra-pr-gate/PR-2121 rejected by Butler

---

1 regressions found
See build details here

---

Found 1 new test failures

Test	Explanation	Runs	Upstream
o.a.c.index.sai.cql.NumericIndexMixedVersionTest.testMultiVersionCompatibilityWithClusteringKeyFiltering (compression)	NEW	🔴	0 / 17

---

Found 6 known test failures

[djatnieks]

This isn't fixing the root cause, rather trying to avoid the JUnit test timeout and let other tests continue.

[djatnieks]

Interestingly, forceWIthDifference failed with the same JUnit timeout in this PR run, meaning the timeout is not happening in the code block that was changed.