KAFKA-17634: Tweak wakeup logic to match WakeupTrigger changes

[AndrewJSchofield]

WakeupTrigger was refactored as a result of changes in AsyncKafkaConsumer. This PR makes the equivalent changes in ShareConsumerImpl.

Committer Checklist (excluded from commit message)

• Verify design and implementation
• Verify test coverage and CI build status
• Verify documentation (including upgrade notes)

[chia7712]

@AndrewJSchofield thanks for this patch. one question: how can we ensure the "match" is maintained in the future as both consumers become more complex? For example, should we refactor WakeupTrigger to reduce the duplicate code?

[AndrewJSchofield]

@chia7712 There are essentially two new consumers based on request managers: AsyncKafkaConsumer and ShareConsumerImpl. They have different client interfaces, but they do share the infrastructure such as use of request managers, a network client delegate and wakeup trigger. Initially, the share consumer has its own heartbeat request manager and membership manager, with far too much code duplication. Now, these have been refactored so almost all of the code is in common.

For WakeupTrigger, there are some patterns that the caller uses to use it properly. ShareConsumerImpl wasn't quite doing it correctly so this PR is correcting that. I'm pretty comfortable with this now and I can't think immediately think of a refactor which will make it much better.