CommandAck parse failed Some required fields are missing

#### Expected behavior

Ack message is normal.

#### Actual behavior

We occasionally encounter the following error when ack message. Once this error occurs, the client cannot recover. The phenomenon is that it will reconnect repeatedly, and the error will still be reported after reconnecting. In the end, it can only be restored by restarting the client.


#### Steps to reproduce

Currently unable to reproduce stably

#### System configuration
go sdk version: 0.12.1
broker version: 2.9.2

Start by reviewing CommandAck parsing in the Go SDK at version 0.12.1 and the reconnect behavior against broker version 2.9.2. Investigate the missing required fields and the repeated reconnect loop; done means the client recovers instead of repeatedly reporting the parse error, with a reliable reproduction or regression coverage.

Written by the indexing model from the issue text.