CNDB-15683: Fix incorrect results when querying mixed AA and EC indexes

[pkolaczk]

When row-aware and non-row-aware indexes are mixed, we now check
the clustering index filter for all the keys that have clustering
information, i.e. keys coming from the row-aware
indexes. Earlier that check was accidentally disabled
if at least one non-row-aware index was used by the query.
That could cause retrieving rows that do not match
the clustering condition of the query.

[github-actions]

Checklist before you submit for review

• 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
100.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-2075 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.VectorSiftSmallTest.testCompaction (compression)	NEW	🔴	0 / 0

---

No known test failures found

[pkolaczk]

I ran this testt 5 times locally and it always passed. Probably a flaky test with a low-probability of failure:

[o.a.c.index.sai.cql.VectorSiftSmallTest.testCompaction (compression)](https://jenkins-stargazer.aws.dsinternal.org/job/ds-cassandra-pr-gate/job/PR-2075/1/testReport/org.apache.cassandra.index.sai.cql/VectorSiftSmallTest)
Post-compaction recall is 0.97

[pkolaczk]

Making CNDB branch for it after merging to avoid additional run of CI, as we already know this is safe to merge (was merged to main).