Clone: Binary Log position and GTID

Specification:
Clone must capture Binary log position and GTID consistent with the snapshot for Local and Remote Clone.

1. After successful clone, performance_schema.clone_status must have the binary log position and GTID filled.

2. After successful Clone and restarting server on cloned data directory, a node should be able to join the cluster.

Development Note:
1. Prototype code from main-MDEV-35248 is to be used.

2. We need to block commit for short time, to capture consistent binary log co-ordinates consistently across all SEs - Similar to BACKUP_LOCK_COMMIT MDL used in Mariabackup. In MySQL, there is GTID persistence in Innodb which avoids this lock.

3. After MDEV-34705 is implemented, we would be able to relax the need for commit lock only for Non-Innodb SE.