Do not update replication data if sanity check fails

[rafael]

Description

• We discovered this error the hard way. Unfortunately, we had a tablet uid collision in our provisioning process and a tablet what spun up with this id. CreateTablet and init_tablet fails correctly, but it has the side effect of registering this newly created tablet (in a different shard) in the data replication topology. This is really dangerous, as now this tablet is shown in two shards (potentially in different keyspaces).
• The following is a fix to do the same sanity check that init_tablet does before trying to UpdateTabletReplicationData.
• This PR also adds a test to avoid future regressions.