[Bug] Georeplication from not partitioned topic cluster to enforced partition cluster

### Search before asking

- [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar.

### Version

2.10.5

### Minimal reproduce step

On a local cluster, create a non-partitioned topic on a cluster with systems topics enabled.

Then, on the remote cluster force all topics to be partitioned.

Then enable georeplication from local to remote clusters.

### What did you expect to see?

Correct replication.

### What did you see instead?

Weird topics were created on the local cluster such as `tenant/namespace/__change_events-partition-0`.

### Anything else?

I also suspect it from duplicating all existing topics to partitioned ones if they weren't.

### Are you willing to submit a PR?

- [ ] I'm willing to submit a PR!

Start by reproducing the behavior with systems topics enabled: create a non-partitioned topic locally, enforce partitioning remotely, and enable georeplication. Trace the georeplication and systems-topic handling involved in creating __change_events-partition-0. Done means replication is correct without creating unexpected topics or duplicating existing non-partitioned topics.

Written by the indexing model from the issue text.