[improve][client] PIP-234: Support sharing the memory limit controller across multiple isolated Pulsar client instances

[oneby-wang]

Fixes apache#25212

Motivation

apache#19074 enables sharing of Pulsar client resources across multiple isolated Pulsar client instances, but this solution lacks limiting the total amount of memory across all of the Pulsar client instances. This PR introduces a shared MemoryLimitController solution for PIP-234.

Modifications

1. Modify MemoryLimitController to support registering multiple trigger callbacks and deregistering the callback when the client instance gets closed.
2. Add shared MemoryLimitController in PulsarClientSharedResources and PulsarClientSharedResourcesBuilder, then apply the shared MemoryLimitController to PulsarClientImplBuilder.
3. Add tests to verify the code change.

Verifying this change

• Make sure that the change passes the CI checks.

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: