[improve][client] Remove default 30s ackTimeout when setting DLQ policy on java consumer

[klevy-toast]

Fixes apache#19134

Motivation

The java client automatically sets a 30s ackTimeout when a deadLetterPolicy is configured. This behavior was added before there was any ability to negativeAcknowledge. Now that negativeAcknowledge exists, it is unnecessary. Furthermore, it is confusing and inconsistent - more details in the issue.

Modifications

Removed setting ackTimeoutMillis in java ConsumerBuilder when a deadLetterPolicy is set.

Verifying this change

• Make sure that the change passes the CI checks.

This change is already covered by existing tests, such as ConsumerBuilderImplTest.

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

If the box was checked, please highlight the changes

• Dependencies (add or upgrade a dependency)
• The public API
• The schema
• The default values of configurations
• The threading model
• The binary protocol
• The REST endpoints
• The admin CLI options
• The metrics
• Anything that affects deployment

Documentation

• doc
• doc-required
• doc-not-needed
• doc-complete

Matching PR in forked repository

PR in forked repository: