[BUG] Judgment criteria for reconnecting the producer

**Describe the bug**
Related to this issue https://github.com/apache/pulsar-client-go/issues/676

https://github.com/apache/pulsar/pull/11804, this PR rewrites the equals method of the Producer, resulting in that when different `pulsar-client-go` uses different port to reconnect, the ` old producer` cannot be removed because the `remoteAddress` will be verified by equals:
``` java
if (producers.remove(producer.getProducerName(), producer)) {
```

https://github.com/apache/pulsar/pull/12846, this pr removes `equals` and will use `hashcode` for judgment. At this time, the
`old producer ` cannot be removed.

The server does not allow different ports to connect to the same producerName. Does it assume that the previous connection will be disconnected first, and the new connection will be established? But the current pulsar-client-go seems to have some problems that the old connection did not handle.

Start by reviewing related issue 676 and pull requests 11804 and 12846, focusing on Producer equality, hashcode, and reconnect behavior. Determine the expected handling when pulsar-client-go reconnects with a different port but the same producerName; done should include a decided criterion that permits the old producer connection to be removed correctly.

Written by the indexing model from the issue text.