Allow replication to different target table

At the moment, HBase replication assumes the source and target table have the same name. Our company is looking into a use case that would require replicating to an arbitrary target table. 

Potential Solution:

It seems that the WALKey stores the table name of it's corresponding edit should be applied to.

We can add a setting to ReplicationPeerConfig that allows users to specify a source to target table mapping. This mapping can then be used to overwrite the WALKey's table before shipping the edit to the target cluster.