CNDB-17275 put using histograms estimations in query planner under flag

[k-rus]

What is the issue

Fixes https://github.com/riptano/cndb/issues/17275

PR #1253 switched query planner to use histograms for rows estimations. This can change query plans in existing databases leading to different performance.

What does this PR fix and why was it fixed

To avoid such change during upgrade a flag, which controls using or not histograms, i.e., old vs new way of estimating rows, is introduced and set to FALSE by default.

The flag is set to TRUE for SAI tests.

[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 failed

Failed conditions
0.0% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud

[cassci-bot]

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

---

13 regressions found
See build details here

---

Found 13 new test failures

Test	Explanation	Runs	Upstream
o.a.c.distributed.test.sai.SlowSAIQueryLoggerTest.testSlowSAIQueryLogger	REGRESSION	🔴🔴	0 / 30
o.a.c.index.sai.QueryContextTest.testWideTableWithStatics[ba] (compression)	REGRESSION	🔵🔴	0 / 30
o.a.c.index.sai.cql.EstimatedRowCountTest.testReturnedRowsEstimates[numShards=16, numPartitions=11] (compression)	REGRESSION	🔵🔴	0 / 30
o.a.c.index.sai.cql.EstimatedRowCountTest.testReturnedRowsEstimates[numShards=2, numPartitions=11] (compression)	REGRESSION	🔵🔴	0 / 30
o.a.c.index.sai.cql.EstimatedRowCountTest.testReturnedRowsEstimates[numShards=4, numPartitions=11] (compression)	REGRESSION	🔵🔴	0 / 30
o.a.c.index.sai.cql.EstimatedRowCountTest.testReturnedRowsEstimates[numShards=64, numPartitions=10,000] (compression)	REGRESSION	🔵🔴	0 / 30
o.a.c.index.sai.cql.EstimatedRowCountTest.testReturnedRowsEstimates[numShards=64, numPartitions=11] (compression)	REGRESSION	🔵🔴	0 / 30
o.a.c.index.sai.cql.EstimatedRowCountTest.testReturnedRowsEstimates[numShards=8, numPartitions=1,000] (compression)	REGRESSION	🔵🔴	0 / 30
o.a.c.index.sai.cql.EstimatedRowCountTest.testReturnedRowsEstimates[numShards=8, numPartitions=11] (compression)	REGRESSION	🔵🔴	0 / 30
o.a.c.index.sai.cql.VectorCompaction100dTest.testZeroOrOneToManyCompaction[version=ec enableNVQ=false]	REGRESSION	🔴🔴	0 / 30
o.a.c.index.sai.cql.VectorSiftSmallTest.testSiftSmall[version=fa enableNVQ=false enableFused=false]	REGRESSION	🔴⚪	0 / 30
o.a.c.index.sai.metrics.QueryMetricsTest.testQueryKindMetrics (compression)	REGRESSION	🔵🔴	0 / 30
o.a.c.index.sai.plan.SingleRestrictionEstimatedRowCountTest.testMemtablesSAI (compression)	REGRESSION	🔵🔴	0 / 30

---

Found 5 known test failures

[pkolaczk]

Sonar seems to have some problem with coverage analysis. I tested coverage manually and QueryController lines are covered by tests.