[Java Client] Fix DLQ message can not send when enable poolMessages

[wangjialing218]

Motivation

Fixes #13269

Modifications

When message is put into possibleSendToDeadLetterTopicMessages, do not clear it in release() since it will be used when send to DLQ later.
And clear the message when it is removed from possibleSendToDeadLetterTopicMessages

Verifying this change

This change is already covered by existing tests, such as PulsarSinkE2ETest.testPulsarSinkDLQ()
just enable poolMessage for client.

Documentation

• no-need-doc

  Only bug fix

[eolivelli]

I wonder if it is possible to not add this new field to MessageImpl.
A new field has a runtime weight.

if the problem is only about not "releasing" the message if it is send to the DLQ, what about simply "retaining" one more time before adding it to the possibleSendToDeadLetterTopicMessages list ?

[wangjialing218]

Only retain byteBuf is not enough. We have to not call recycle() in release() if the message was added to possibleSendToDeadLetterTopicMessages list.

If message is acked by consumer as normal case, the message will not be added to possibleSendToDeadLetterTopicMessages list and should be clear in release().

So how could we known whether this message was added to possibleSendToDeadLetterTopicMessages list when user call release()? If there is a way then we could remove this field.

[github-actions]

The pr had no activity for 30 days, mark with Stale label.

[github-actions]

The pr had no activity for 30 days, mark with Stale label.