"02/03/2022 Unable to refresh a VDB that is setup for replication - Master / Slave"

[ranjeethdelphix]

** Expected Behavior**
Rewind of VDBs should be able seamless and retain the original state of the database including replication

** Actual Behavior**
A VDB that is either master or slave to another VDB / DB is not able to retain replication status after rewind

Steps To Reproduce the Problem
Rewind and VDB that is configured as replication slave
OR
Rewind and VDB that is configured as replication master

Steps to reproduce the behavior:

1. Take a snapshot of the VDB after setting up replication - master / slave'
2. Rewind VDB to the snapshot
3. VDBs are rolled back to the snapshot but the replication slave status is lost
4. See the replication status using "Show slave status\g" on slave VDB

Version
MySQL 5.7.19
MySQL 5.7.34

Additional Context
Refreshes are expected to lose the replication status because the refresh copies the DB state from dSource. However, rewind is expected to rollback to the replication status unlike refresh from dSource.