Fix MariaDB fetching of default table character-set

[grooverdan]

Q	A
Type	bug
Fixed issues	#6361

Summary

From MariaDB-10.10.1, where uca1400 was added, the information_schema.COLLATION_CHARACTER_SET_APPLICABILITY was extended to have FULL_COLLATION_NAME which corresponds to the information_schema.TABLES.TABLE_COLLATION value.

Executable comment syntax is used to limited to the applicable versions.

To preserve compatibility with older MariaDB versions, and MySQL versions where the previous COLLATION_NAME was the match is left as a JOIN criteria. In new MariaDB versions this won't result in an extra row match.

Closes: #6361

The lack of this fix did case the CI test to fail with a MariaDB-11.0+ container:

1) Doctrine\DBAL\Tests\Functional\Schema\MySQLSchemaManagerTest::testEnsureTableWithoutOptionsAreReflectedInMetadata
Undefined array key "engine"

/home/runner/work/dbal/dbal/src/Schema/Table.php:927
/home/runner/work/dbal/dbal/tests/Functional/Schema/MySQLSchemaManagerTest.php:550

With this fix all version of MySQL and MariaDB (even those new ones soon to be in a different PR) will pass like: https://github.com/grooverdan/dbal/actions/runs/9412110648/job/25926481038

[grooverdan]

SQL example:

MariaDB [test]> select version();
+----------------+
| version()      |
+----------------+
| 11.5.2-MariaDB |
+----------------+
1 row in set (0.001 sec)


MariaDB [test]> create table t (c varchar(30)) charset 'utf32' collate 'uca1400_ai_ci';
Query OK, 0 rows affected (0.002 sec)

MariaDB [test]> SELECT t.TABLE_NAME,            t.ENGINE,            t.AUTO_INCREMENT,            t.TABLE_COMMENT,            t.CREATE_OPTIONS,            t.TABLE_COLLATION,            ccsa.CHARACTER_SET_NAME       FROM information_schema.TABLES t         INNER JOIN information_schema.COLLATION_CHARACTER_SET_APPLICABILITY ccsa             ON /*M!101001 ccsa.FULL_COLLATION_NAME = t.TABLE_COLLATION OR */ COLLATION_NAME = t.TABLE_COLLATION WHERE t.TABLE_NAME='t';
+------------+--------+----------------+---------------+----------------+---------------------+--------------------+
| TABLE_NAME | ENGINE | AUTO_INCREMENT | TABLE_COMMENT | CREATE_OPTIONS | TABLE_COLLATION     | CHARACTER_SET_NAME |
+------------+--------+----------------+---------------+----------------+---------------------+--------------------+
| t          | InnoDB |           NULL |               |                | utf32_uca1400_ai_ci | utf32              |
+------------+--------+----------------+---------------+----------------+---------------------+--------------------+

[derrabus]

I'd like to avoid version conditionals in SQL. We have our platform class hierarchy for this purpose.

I'll accept this change as a hotfix for MariaDB 11.4 on the 3.8.x branch. Can you work on a PR for 3.9.x that moves the SQL statement to AbstractMySQLPlatform and that introduces a new platform class for MariaDB 10.10 which overrides the generated SQL?