CNDB-12683 make name validation functions clear

[k-rus]

What is the issue

The names of functions validating schema object names are missing semantics and placed in different files. This led to incorrect use of them and to https://github.com/riptano/cndb/issues/12451, https://github.com/riptano/cndb/issues/12683, https://github.com/riptano/cndb/issues/13007, https://github.com/riptano/cndb/issues/13043.

What does this PR fix and why was it fixed

This PR improves names of the name validation functions with their actual semantics. It also co-locates them in a single files. The error messages are fixed accordently.

This PR also makes minor change to a long table name test to use the keyspace name reported in an incident.

[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

[sonarqubecloud]

Quality Gate passed

Issues
4 New issues
0 Accepted issues

Measures
0 Security Hotspots
85.7% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[cassci-bot]

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

---

4 new test failure(s) in 1 builds
See build details here

---

Found 4 new test failures

Test	Explanation	Branch history	Upstream history
...tiveControllerTest.testLongTableNameFromOptions	regression	🔴	🔵🔵🔵🔵
...tionControllerConfigTest.testStoreLongTableName	regression	🔴	🔵
...bleValidationTest.testCreatingTableWithLongName	regression	🔴	🔵🔵🔵🔵
o.a.c.u.b.BinLogTest.testTruncationReleasesLogS...	regression	🔴	🔵🔵🔵🔵🔵🔵🔵

---

Found 1 known test failures