[feature request] C++ and Python client support consumer memory limits.

### Search before asking

- [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar.

### Motivation

[PIP-74](https://github.com/apache/pulsar/wiki/PIP-74%3A-Pulsar-client-memory-limits)

C++ client consumers have not implemented memory limits yet.

### Solution

There are several key points to achieving this feature.
1. Reconstructing the consumer structure.
- https://github.com/apache/pulsar/pull/16969
- Abstract `ConsumerBase`, put together some common logic.
2. Refactoring single-consumer and MultiTopicConsumer transports type.
- In the current implementation of C++, messages are sent to multi-topic consumers by blocking queue + listener, which is an old historical implementation. If you want to achieve memory limits, you need to do the same as the current java implementation, let `MuiltiTopicConsumer` take the initiative to control the message.

### Alternatives

Here's an imperfect draft: https://github.com/apache/pulsar/pull/16933

### Anything else?

_No response_

### Are you willing to submit a PR?

- [x] I'm willing to submit a PR!

Empieza por PIP-74 y los cambios en ConsumerBase y MultiTopicConsumer descritos en PR 16969, y después compara el borrador imperfecto de PR 16933. Se considera terminado cuando se haya definido e implementado el control del límite de memoria del consumidor para los clientes C++ y Python solicitados, incluido el recorrido de MultiTopicConsumer.

Escrito por el modelo de indexación a partir del texto del issue.