CNDB-13742 ReadCallback logs when replica doesn't respond

[zgorzalyj]

Summary

https://github.com/riptano/cndb/issues/13742
Lack of information when replica doesn't respond.
Changes

Add new log which contains information about 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
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[driftx]

Left one question but it looks good.

[driftx]

Being inside this block will require that tracing is enabled, which is different from trace level logging (which would also need to be enabled.) Is that intended?

[zgorzalyj]

Yes, this is intentional. The production code logs these details inside Tracing.isTracing() conditional blocks, so the logs only appear when tracing is actively enabled for a session, not just when TRACE log level is configured. This keeps log volume minimal in production while still allowing targeted debugging through tracing when needed.