Drop support for DatabaseOrdinary in MaterializedMySQL

[stigsb]

The default database engine has been "Atomic" since ClickHouse 20.10. To improve maintainability of the experimental MaterializedMySQL feature, this PR drops support for the "Ordinary" engine for backing MaterializedMySQL.

Also get rid of thread name logic for StorageMaterializeMySQL wrapping, use setInternalQuery instead (similar to MaterializedPostgreSQL).

Changelog category (leave one):

• Build/Testing/Packaging Improvement

Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
Drop support for using Ordinary databases with MaterializedMySQL

Detailed description / Documentation draft:

By adding documentation, you'll allow users to try your new feature immediately, not when someone else will have time to document it later. Documentation is necessary for all features that affect user experience in any way. You can add brief documentation draft above, or add documentation right into your patch as Markdown files in docs folder.

If you are doing this for the first time, it's recommended to read the lightweight Contributing to ClickHouse Documentation guide first.

Information about CI checks: https://clickhouse.tech/docs/en/development/continuous-integration/

[tavplubix]

Unrelated failures:
Stress test (thread) - #31423
Integration tests were broken in master

Related failures:
ClickHouse special build check
Stress tests (debug, actions) - can be reproduced with ClickHouse/tests$ ./clickhouse-test --db-engine="Replicated('/test/repl/db/123', 's1', 'r1')" 01185_create_or_replace_table

[tavplubix]

ClickHouse special build check and Stress test (debug, actions) failures are related to changes in the PR, @stigsb, could you please fix it?

[stigsb]

Yes, I'll look at it today.

[stigsb]

@tavplubix looking at the remaining test failures:

"Fast test" seems to fail because the Raft port is already taken (could be a recent process exiting uncleanly?)

"Stress test (thread, actions)" has a failing test script, but I can't make out why from the logs. Any ideas @tavplubix ?

[tavplubix]

Tests failures are unrelated to changes