MaxScale detects wrong server character set

MariaDB 10.10 now includes collations that do not have an ID and the value of collation_server may not be found in information_schema.collations. The docker image of MariaDB 11.4.2 now uses the UCA collations by default that do not have a character set and MaxScale will wrongly detect the server character set as big5_chinese_ci since it's the first in the list.