WL#11046: Improve test coverage for online alter index and multiple triggers on a single table in RPL & GR

Replication and GR use distributed environment and its essential we ensure this
works. Currently we have no coverage for on-line alter index and limited for
multiple triggers (part of 5.7) with replication and GR.

FR1   : Tests must verify that ALTER TABLE..RENAME INDEX is replicated through 
replication.
FR1.1 : Tests must ensure that index is correctly renamed on both master and slave 
using ALTER TABLE..RENAME INDEX.

FR2   : Tests must verify that ALTER TABLE..RENAME INDEX is replicated through 
group replication.
FR2.1 : Tests must ensure that index is correctly renamed across all group members 
using ALTER TABLE..RENAME INDEX.

FR3   : Tests must ensure that multiple triggers created on a table for an action 
and timing are successfully replicated on slave.
FR3.1 : Tests must ensure that ACTION_ORDER and CREATED attributes are preserved 
across master and slave.

FR4   : Tests must ensure that multiple triggers created on a table for an action 
and timing are successfully replicated across all members in the group.
FR4.1 : Tests must ensure that ACTION_ORDER and CREATED attributes are preserved 
across all group members.

A)   Verify that ALTER TABLE..RENAME INDEX is replicated successfully to slave.
A.1) Create a table on master, create a index on the table.
A.2) Rename the index using ALTER TABLE..RENAME INDEX command.
A.3) Ensure that the index is renamed successfully on master and slave.
Verify the same for spatial, full_text indexes.

B)   Verify that ALTER TABLE..RENAME INDEX is replicated successfully with GR.
B.1) Create a table on a group member, create a index on the table.
B.2) Rename the index using ALTER TABLE..RENAME INDEX command.
B.3) Ensure that the index is renamed successfully across all group members.
Verify the same for spatial, full_text indexes.

C)   Verify the behavior of multiple triggers on a table with replication.
C.1) Create a table on master, create multiple triggers on the table for same 
action (INSERT/UPDATE/DELETE) and timing (BEFORE/AFTER).
C.2) Ensure that create trigger statement is replicated successfully on to the 
slave.
C.3) Ensure that ACTION_ORDER, CREATED attributes are same on master and slave for 
a trigger.
C.4) Perform some DML operations on table such that triggers are triggered.
C.5) Ensure that data is consistent on master and slave.

D)   Verify the behavior of multiple triggers on a table with GR.
D.1) Create a table on a primary member, create multiple triggers on the table for 
same action (INSERT/UPDATE/DELETE) and timing (BEFORE/AFTER).
D.2) Ensure that create trigger statement is replicated successfully on all group 
members.
D.3) Ensure that ACTION_ORDER, CREATED attributes are same across group for a 
trigger.
D.4) Perform some DML operations on table such that triggers are triggered.
D.5) Ensure that data is consistent across all the group members.