Semi-sync Replica Can't Kill Dump Thread When Using SSL

When a replica stops an established semi-sync connection (e.g. from running STOP REPLICA/STOP SLAVE), it is supposed to kill the corresponding binlog dump thread on the primary server. This is done by the replica creating a new connection to its primary which issues a KILL command targeting the established connection. However, when connections are configured to use SSL, this new connection created by the replica to kill the dump thread doesn't have any logic to configure SSL options, and thereby the connection can't be made, and the dump thread will never be killed.

This may cause:
1. Unexpected long-running transactions which commit while the replica disconnects to pause until the configured rpl_semi_sync_master_timeout is exceeded
2. User confusion or scripts to break, as the behavior is not consistent.

Note that this issue spawned from a test failure during a merge to 11.4, where MDEV-31857 enabled --ssl-verify-server-cert by default.