After enabled geo-replication, we are not able to produce messages to a partitioned non-persistent topic.

Reproduce step:

1. Start a geo-replication instance with 2 clusters, I have 3 brokers for each cluster
2. Create a non-persistent partitioned topic such as 10 partitions
3. Use pulsar-perf to publish messages to the partitioned topic
4. Verify if the message produce throughput is 0, such as `bin/pulsar-perf produce -s 2048 -r 100 -bm 1 non-persistent://public/default/test`

The root cause is there are 2 places calling a sync method in the async method callback.
So the fix is:

1. Async the `validatePartitionedTopicAsync` method
2. Avoid call get cluster sync method when getting the replication client

Integration tests added.

…en creating partitioned-topic, this will cause dead thread problem.