Use a separate WAL provider for hbase:replication table

TestMultiSlaveReplication fails when using table based replication queue storage

The test uses a small wal rolling size for testing more operations

    // smaller block size and capacity to trigger more operations
    // and test them
    conf1.setInt("hbase.regionserver.hlog.blocksize", 1024 * 20);
    conf1.setInt("replication.source.size.capacity", 1024);

But after moving to table based replication queue storage, the update to hbase:replication tablr will also be append to the same WAL file, so it will make the replicaton worker move forward, and then it will update the hbase:replication table since the offset has been changed, so then it will make the replication work again, and so on...

This will make the wal file size reach the configured size easily and trigger unexpected wal rolling, and then fail the test.

For fixing the test, we can increase the wal rolling size, or we can use multi wal, to separate the wal files of hbase:replication table along. so it will not mess up the normal wal files.