CNDB-16277: Fix TombstoneOverwhelmingException being swallowed when tracking warnings

[driftx]

What is the issue

ReadCommandVerbHandler was catching RejectException and returning an empty response instead of propagating the failure when warnings tracking was enabled.

What does this PR fix and why was it fixed

TombstoneOverwhelmingException is always re-thrown regardless of warning tracking state.

[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
60.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-2171 rejected by Butler

---

8 regressions found
See build details here

---

Found 8 new test failures

Test	Explanation	Runs	Upstream
o.a.c.config.DatabaseDescriptorRefTest.testDatabaseDescriptorRef (compression)	NEW	🔴	0 / 26
o.a.c.cql3.validation.operations.AggregationQueriesTest.testAggregationQueryShouldNotTimeoutWhenItExceedesReadTimeout (compression)	NEW	🔴	2 / 26
o.a.c.index.SecondaryIndexManagerTest.testIndexRebuildWhenAddingSStableViaRemoteReload (compression)	NEW	🔴	20 / 26
o.a.c.index.sai.cql.GeoDistanceAccuracyTest.haversineBenchmark (compression)	NEW	🔴	0 / 26
o.a.c.metrics.TrieMemtableMetricsTest.testContentionMetrics (compression)	NEW	🔴	9 / 26
o.a.c.repair.FailedAckTest.failedAck ()	NEW	🔴	0 / 26
o.a.c.repair.FailingRepairFuzzTest.failingRepair ()	NEW	🔴	0 / 26
o.a.c.repair.SlowMessageFuzzTest.slowMessages (compression)	NEW	🔴	0 / 26

---

Found 3 known test failures

[michaelsembwever]

should be upstreamed too ?

[driftx]

Will do that after merge so I can reference the commit.

[michaelsembwever]

Will do that after merge so I can reference the commit.

It's also nice to have the cassandra ticket id in the commit msg (so the rebaser on the next rebase knows whether to keep or skip the commit).
(I'm thinking if that's our practice then it removes any pressure of actually merging that ticket, let it be lazy and opportunistic)
(not important for this pr, just discussion)