CNDB-17831: Use 2038 max deletion time in HCD_1

[driftx]

What is the issue

Max deletion time is 2038 in 4.0 and should be used in HCD_1 mode

What does this PR fix and why was it fixed

Use 2038 max deletion time in HCD_1

[github-actions]

Checklist before you submit for review

• This PR adheres to the Definition of Done
• Make sure there is a PR and ticket 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 IBM copyright header instead of the Apache License one (no DataStax copyright any longer)

[djatnieks]

I think this change is breaking testImprovedMaxTTL - maybe the Assume needs to be updated to something like this?
Assume.assumeFalse(DatabaseDescriptor.getStorageCompatibilityMode().isBefore(5));

[driftx]

Yep, good call, added.

[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

[plpesvc-ds]

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

---

3 regressions found
See build details here

---

Found 3 new test failures

Test	Explanation	Runs	Upstream
replica_side_filtering_test.TestAllowFiltering.test_consistent_skinny_table (offheap-bti-scm-hcd_1)	REGRESSION	🔵🔴	0 / 30
o.a.c.index.sai.cql.VectorCompaction100dTest.testZeroOrOneToManyCompaction[version=ec enableNVQ=false] ()	NEW	🔴⚪	0 / 30
o.a.c.index.sai.cql.VectorSiftSmallTest.testRerankKZeroOrderMatchesFullPrecisionSimilarity[version=fa enableNVQ=false enableFused=false] ()	NEW	🔴⚪	0 / 30

---

Found 8 known test failures