[Bug] ns-isolation-policy takes a long time take effect

### Search before asking

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

### Version

3.0.0

### Minimal reproduce step

I want to set a isolation policy for a namespace, i execyted ns-isolation-policy command, but i can get a error when i execute partitioned-lookup command, refer to the figure below for details.


i tried to produce messages to this topic, it also cann't works, and give a error.

### What did you expect to see?

The topic in the namespace belongs can be assigned to the broker on port 8080

### What did you see instead?

Refer to the screenshot above for the problem

### Anything else?

_No response_

### Are you willing to submit a PR?

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

Start by reproducing the behavior with the ns-isolation-policy and partitioned-lookup commands described in the issue, then compare the namespace policy update with topic assignment and message production. Done means the namespace topic can be assigned to the broker on port 8080 without the reported lookup or production errors.

Written by the indexing model from the issue text.