[improve][client] Clean up unacked message tracker when topics are removed in multi-topic consumers

[Dream95]

Motivation

Follow-up to [#25921]. That PR fixed incorrect unacked-message removal on explicit unsubscribe by comparing base partitioned topic names instead of substring matching. This change extends the same cleanup to other paths where a multi-topic or pattern consumer drops a topic without calling unsubscribe, so timed-out unacked entries are not left behind.

In production, topics can also disappear from a consumer when:

• Partition metadata shrinks — onTopicsExtended closes partition consumers when a partitioned topic is deleted or loses partitions (autoUpdatePartitions).
• Pattern subscription — PatternMultiTopicsConsumerImpl removes a grouped partitioned topic after all its partition consumers are gone.

Those paths closed partition consumers but did not clear matching entries from the unacked tracker.

Modifications

• Extract removeTopicMessagesFromUnackedTracker(String topicName) in MultiTopicsConsumerImpl and reuse it from unsubscribeAsync .
• After partition consumers are closed in onTopicsExtended when partition count goes to zero, call removeTopicMessagesFromUnackedTracker for the logical topic name.
• In PatternMultiTopicsConsumerImpl, when all partitions of a grouped topic are removed, call the same helper before dropping the topic from partitionedTopics.

Verifying this change

• Make sure that the change passes the CI checks.

(Please pick either of the following options)

This change added tests and can be verified as follows:

./gradlew :pulsar-client-original:test --tests "org.apache.pulsar.client.impl.MultiTopicsConsumerImplTest.testOnTopicsExtendedRemovedTopicCleansUnackedMessages"
./gradlew :pulsar-client-original:test --tests "org.apache.pulsar.client.impl.PatternMultiTopicsConsumerImplTest#testOnTopicsRemovedCleansUnackedMessagesForRemovedPartitionedTopic"

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

Matching PR in forked repository

PR in forked repository: Dream95#13