We need a size limit for cache of single managedLeger

### Search before asking

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

### Motivation

When a topic produce too much messages, the caches of broker will be full with this topic. In this case, the fetch request of other consumers cannot hit the cache and they only can read entries by bookeeper.

### Solution

Add a size limit for cache of single managedLedger.

### Alternatives

~

### Anything else?

~

### Are you willing to submit a PR?

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

Start by tracing the broker cache and ManagedLedger cache implementation and its configuration points; the issue does not name files or tests. Compare how cache usage is tracked per managed ledger and identify existing cache-related tests. Done means a single managed ledger has an enforced size limit so other consumers can still use the broker cache.

Written by the indexing model from the issue text.