[12.x] Add option to disable MySQL ssl when restoring or squashing migrations

[andersonls]

Newer versions of the MySQL client are enforcing a more strict SSL certificate check and resulting in the following error when squashing migrations or running migrate:fresh

ERROR 2026 (HY000): TLS/SSL error: self-signed certificate in certificate chain

Currently, to bypass this error we need to edit the MySQL config file. To make things easier, this PR adds a new option to disable SSL when executing the commands to dump/restore MySQL database.

[Jellyfrog]

I don't think this is correct at all @andersonls, --ssl is both deprecated and removed in newer Mysql releases, and not a mysql argument, it's for mysqld. ssl-mode seems to be the argument you're looking for https://dev.mysql.com/doc/refman/8.0/en/connection-options.html#option_general_ssl-mode

$ mysql -V
mysql  Ver 14.14 Distrib 8.0.0-dmr, for Linux (x86_64) using  EditLine wrapper
$ mysql --ssl=off
mysql: [ERROR] unknown variable 'ssl=off'

[andersonls]

@Jellyfrog please check #55758, there is a WIP fixing this. My system was aliasing the mysql exec to mariadb and mariadb still uses the --ssl=off option.

[gazben]

@taylorotwell Why was this change reverted here? 1bfad30

With the new Debian 13 release, the mariadb-dump command defaults to ssl, and there is no way to modify the connection string to add the --skip-ssl flag to the baseDumpCommand() function.

[andersonls]

@gazben in short, because the --ssl=off option is for the mariaDb client, the native MySQL client uses a different option. As a workaround you can disable in the config file