Use master_retry_count to fix rpl.rpl_semi_sync_master_crash_if_active_trxs

Summary:
The proper variable to adjust is master_retry_count, not
master_connect_retry.

Squash with D5841339

Test Plan:
mtr rpl.rpl_semi_sync_master_crash_if_active_trxs
verify show slave status with master_retry_count

Reviewers: abhinavsharma, mung

Reviewed By: abhinavsharma

Subscribers: webscalesql-eng@fb.com

Differential Revision: https://phabricator.intern.facebook.com/D7317422

Tasks: T26970848

Signature: 7317422:1521409002:c971567f5688f55dc775d06e63d1da8371074c00

Author: Herman Lee

mysql-test/suite/rpl/r/rpl_semi_sync_master_crash_if_active_trxs.result

@@ -8,7 +8,7 @@ call mtr.add_suppression("Force shutdown: Semi-sync master is being switched off
 create table t1(a int) engine=innodb;
 include/stop_slave.inc
 SET GLOBAL DEBUG='+d,dont_send_semi_sync_reply';
-CHANGE MASTER TO MASTER_CONNECT_RETRY=0;
+CHANGE MASTER TO MASTER_RETRY_COUNT=0;
 include/start_slave.inc
 insert into t1 values(1);
 ERROR HY000: Lost connection to MySQL server during query

mysql-test/suite/rpl/t/rpl_semi_sync_master_crash_if_active_trxs.test

@@ -13,7 +13,7 @@ sync_slave_with_master;
 connection slave;
 source include/stop_slave.inc;
 SET GLOBAL DEBUG='+d,dont_send_semi_sync_reply';
-CHANGE MASTER TO MASTER_CONNECT_RETRY=0;
+CHANGE MASTER TO MASTER_RETRY_COUNT=0;
 source include/start_slave.inc;
 
 ##