Add highest sequenceId for CommandSendReceipt. (#5653)
## Motivation
Since #5491 merged, while user use new pulsar client to produce batch messages to older version broker(e.g. 2.4.0), send ack error will occur:
```
[pulsar-client-io-8-2] WARN org.apache.pulsar.client.impl.ProducerImpl - [persistent://sandbox/pressure-test/test-A-partition-11] [pulsar-cluster-test-13-294] Got ack for msg. expecting: 13 - got: 224 - queue-size: 9
```
The problem is client use highest sequence id to match the response sequence id, but in old version broker can not return the highest id.
So, this pr is try to fix the problem of produce batch message with new version client and old version broker.
### Modifications
Add highest sequence id to CommandSendReceipt. If the response highest sequence id of send receipt > lowest sequence id, it means broker is a new version broker, so we need to verify the highest sequence id, otherwise we only verify the lowest sequence id.
9 files changed
