Clone: Support Remote Clone Replacing Current Data Directory

Specification:
All conditions being similar to MDEV-36742, skip data directory clause in syntax to rplace the current data directory. Server is stopped after the clone. On restart, it starts with the cloned data. Existing data on the recipient instance is removed.

1. Support cloning Donor data to replace Recipient Data directory.

CLONE INSTANCE FROM clone@<Donor IP>:<Donor PORT>

IDENTIFIED BY 'clone_pass';

2. Support automatic restart of the recipient server after clone, when server is managed by mariadb-safe.

3. Support Data Flow and Network Control Configurations

| clone_delay_after_data_drop |

| clone_enable_compression|

| clone_max_data_bandwidth|

| clone_max_network_bandwidth|

4. Support automatic restart after a network failure while cloning Innodb - Have configuration to control the maximum network outage time.

|clone_donor_timeout_after_network_failure|

Limitations:
All Limitations of MDEV-36733 apply.

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

2. Unlike MySQL, MariaDB don't support RESTART command. We need to set the exit code while shutting down the server so that mariadb-safe or any other process managing the server can restart it automatically.

3. Enable and Disable restarting based on SE being cloned. Restart would be supported only during Innodb clone.

4. All related mtr tests must be ported from MySQL. Must work on all platforms(CI).