[Enhancement] optimization transcation msg endTransaction in 5.x proxy

### Before Creating the Enhancement Request

- [x] I have confirmed that this should be classified as an enhancement rather than a bug/feature.

### Summary

endTransaction can use tranStateTableOffset and commitLogOffset in requestheader if 5.x proxy has no info(eg, proxy restart) which avoids endTransaction failure.

### Motivation

In 5.x version, if client send transcation msg but does not use the same proxy to commit, the msg will lost.
1. the client may commit half message in different proxy from send, such as client reconnect when proxy restart
2.The client uses the domain name to send transaction messages, but uses the IP under the domain name when submitting, resulting in different proxies when sending and submitting.
3. transaction info not only exists in the proxy that sent the message also in EndTransactionRequest header. If the proxy does not have this information, we can also use the request header
### Describe the Solution You'd Like

in this endTransaction in proxy, we add two param commitLogOffset and tranStateTableOffset

### Describe Alternatives You've Considered

no

### Additional Context

_No response_