[BUG] Cannot acknowledge messages that come in without a topicName in MessageID

### Description

Depending on the producer (fs-client, java, KOP etc) sometimes messages come in without a topicName inside MessageID

Acknowledging this type of message breaks in
await _subConsumers[messageId.Topic].Acknowledge(messageId, cancellationToken).ConfigureAwait(false);
because messageId.Topic == ""

the consumer already has the topicName and I think the Acknowledge should create the topicName based on the other fields if the topicName is missing.

### Reproduction Steps

.

### Expected behavior

.

### Actual behavior

.

### Regression?

_No response_

### Known Workarounds
Recreating the messageID is a work-around for this issue.
```
var ackM = new MessageId(message.MessageId.LedgerId,
message.MessageId.EntryId,
message.MessageId.Partition,
message.MessageId.BatchIndex,
$"{_consumer.Topic}-partition-{message.MessageId.Partition}");
await _consumer!.Acknowledge(ackM);
```
### Configuration

_No response_

### Other information

_No response_

Start at the _subConsumers[messageId.Topic].Acknowledge call and inspect MessageId handling when Topic is empty. Reproduce the failure with a message lacking topicName, then verify that acknowledgement succeeds without recreating the MessageId.

Written by the indexing model from the issue text.