CNDB-15632: CNDB-15157: limit log lines during commitlog replay (#2001)

[michaelsembwever]

https://github.com/riptano/cndb/issues/15632

Port into main-5.0 commit b9c402b

NDB-15157: limit log lines during commitlog replay (https://github.com/datastax/cassandra/pull/2001)
### What is the issue

Very long log lines can be produced during commitlog replay

### What does this PR fix and why was it fixed

Limits the amount of information printed at debug, but retains full
information at trace

[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
86.4% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[cassci-bot]

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

---

2 regressions found
See build details here

---

Found 2 new test failures

Test	Explanation	Runs	Upstream
o.a.c.cql3.SimpleQueryTest.test2ndaryIndexBug (compression)	REGRESSION	🔴🔵	0 / 10
o.a.c.cql3.validation.operations.AggregationQueriesTest.testAggregationQueryShouldNotTimeoutWhenItExceedesReadTimeout (compression)	REGRESSION	🔴🔴	2 / 10

---

Found 5 known test failures