Topic partition's segmented storage space calculation error

**Describe the bug**
The storage space of partition is much larger than 4G and entries is much larger than 50000 (managedLedgerMaxSizePerLedgerMbytes=4096, managedLedgerMaxEntriesPerLedger=50000 in broker.conf).

Pulsar v2.8.1

broker.conf
managedLedgerMaxEntriesPerLedger=50000
managedLedgerMaxSizePerLedgerMbytes=4096

```
producer code:
producer = client.newProducer(Schema.STRING)
.topic(topic)
.producerName(producerName)
.sendTimeout(0, TimeUnit.SECONDS)
.enableBatching(true)
.batchingMaxMessages(1000)
.compressionType(CompressionType.ZSTD)
.blockIfQueueFull(true)
.create();
```

**To Reproduce**
Steps to reproduce the behavior:
1. Start producer
2. View the segmented storage of the partition in pulsar manager
3. The storage space of partition is much larger than 4G

Start with the broker.conf limits and the Java producer settings, then reproduce the partition in Pulsar Manager as described. Compare the displayed segmented storage and entry counts with the configured limits; done means the partition no longer exceeds the expected 4G or 50,000-entry thresholds and the behavior is covered by a regression test.

Written by the indexing model from the issue text.