[C++] Fix the consumer configuration inconsistency with Java client

[BewareMyPower]

Motivation

#13627 supports chunking messages for C++ client. However, the consumer configuration AutoOldestChunkedMessageOnQueueFull has a typo that it doesn't contain the Ack. See the corresponding Java configuration:

pulsar/pulsar-client-api/src/main/java/org/apache/pulsar/client/api/ConsumerBuilder.java

Line 733 in d111476

ConsumerBuilder<T> autoAckOldestChunkedMessageOnQueueFull(boolean autoAckOldestChunkedMessageOnQueueFull);

In addition, the default value of maxPendingChunkedMessages is 10 in Java client implementation but 100 in JavaDocs. The C++ client followed the JavaDocs and set the default value of maxPendingChunkedMessages 100. But it's better to keep the consistency with Java client's implementation instead of the wrong JavaDocs.

Since #13627 is not included in any release now, we should include this fix before 2.10.0 release.

Modifications

• Change setAutoOldestChunkedMessageOnQueueFull to setAutoAckOldestChunkedMessageOnQueueFull.
• Change isAutoOldestChunkedMessageOnQueueFull to isAutoAckOldestChunkedMessageOnQueueFull.
• Change the default value of maxPendingChunkedMessage to 10.

Verifying this change

• Make sure that the change passes the CI checks.

This change is a trivial rework / code cleanup without any test coverage.

Does this pull request potentially affect one of the following parts:

If yes was chosen, please highlight the changes

• Dependencies (does it add or upgrade a dependency): (yes / no)
• The public API: (yes)
• The schema: (yes / no / don't know)
• The default values of configurations: (yes / no)
• The wire protocol: (yes / no)
• The rest endpoints: (yes / no)
• The admin cli options: (yes / no)
• Anything that affects deployment: (yes / no / don't know)