SkySQL Docker - Update MaxScale configuration to take advantage of newer features

MaxScale has a lot of features that create differentiation and competitive advantages for SkySQL. This is request is to simply change some of the defaults.

Master reconnection
Allows MaxScale to migrate connections from the old primary to the new primary so applications don't have to open new ones.

https://mariadb.com/kb/en/mariadb-maxscale-24-readwritesplit/#master_reconnection

Adapting routing
Allows MaxScale to route queries based on individual instance response times.

https://mariadb.com/kb/en/mariadb-maxscale-24-readwritesplit/#slave_selection_criteria

Delayed retry
Allows MaxScale to retry reads if they fail due to a connection error (e.g., the replica just failed).
We may want to set the read timeout to a smaller value (10s by default)

https://mariadb.com/kb/en/mariadb-maxscale-24-readwritesplit/#retry_failed_reads
https://mariadb.com/kb/en/mariadb-maxscale-24-readwritesplit/#delayed_retry_timeout

Transaction replay
Allows MaxScale to replay transactions on the new primary if the original fails.

https://mariadb.com/kb/en/mariadb-maxscale-24-readwritesplit/#transaction_replay

Causal reads
Allows MaxScale to tell a replica to catch up to the client before executing the query.
We may want to set the read timeout to a smaller value (10s by default)

https://mariadb.com/kb/en/mariadb-maxscale-24-readwritesplit/#causal_reads
https://mariadb.com/kb/en/mariadb-maxscale-24-readwritesplit/#causal_reads_timeout