[improve] [client] improve the class GetTopicsResult

[poorbarcode]

Motivation

Background

1.Regarding the API getting topics by regexp pattern, there are two implementations:*

• List<String> HttpLookupService.getPartitionedTopicMetadata(...)
• CommandGetTopicsOfNamespace BinaryProtoLookupService.getPartitionedTopicMetadata(...)

Pulsar transferred both response types List<String> and CommandGetTopicsOfNamespace to a GetTopicsResult object. And discarded the partition information when doing transference. For example:

• Get a list topic-1-partition-0, topic-1-partition-1.
• The transferring operation will group them to topic-1.

2.The behavior of Patten consumers

• Before Allow for topic deletions with regex consumers #5230, Patten consumers will try to create the missing partitions when it starts up.
• After Allow for topic deletions with regex consumers #5230, Patten consumers only subscribe to the partitions that exist to lead the topics can be deleted automatically. In other words, it sets the variable createTopicIfDoesNotExist of Multi Topics Consumer to false.

---

Issue

1. When users are starting a Pattern consumer, the consumer will try to subscribe to all the partitions even if some partitions have been deleted before, and then the client crashes due to a Topic Not Exists Exception. You can reproduce the issue by the test testConsumerAfterOnePartDeleted
2. The Patten consumer that is started removes all partitions when one partition was deleted, even if there are still half of the partitions exist.

---

Modifications

I will submit three PRs to solve the two issues above.

• (The current PR) Improve the GetTopicsResult, so we can get the original partitions of partitioned topics
• (Following PR) Multi Topics Consumer only subscribes to the existing partitions if the config createTopicIfDoesNotExist is false.
• (Following PR) The Patten consumer that is started only removes the partitions that were deleted.

Documentation

• doc
• doc-required
• doc-not-needed
• doc-complete

Matching PR in forked repository

PR in forked repository: x

[poorbarcode]

/pulsarbot rerun-failure-checks

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 82.50000% with 7 lines in your changes are missing coverage. Please review.

Project coverage is 73.22%. Comparing base (bbc6224) to head (f0ce2b2).
Report is 301 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff              @@
##             master   #22766      +/-   ##
============================================
- Coverage     73.57%   73.22%   -0.35%     
+ Complexity    32624    32611      -13     
============================================
  Files          1877     1890      +13     
  Lines        139502   141522    +2020     
  Branches      15299    15534     +235     
============================================
+ Hits         102638   103633     +995     
- Misses        28908    29885     +977     
- Partials       7956     8004      +48     

Flag	Coverage Δ
inttests	27.45% <0.00%> (+2.86%)	⬆️
systests	24.78% <45.00%> (+0.46%)	⬆️
unittests	72.23% <82.50%> (-0.62%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files	Coverage Δ
...g/apache/pulsar/client/impl/HttpLookupService.java	84.11% <100.00%> (+2.86%)	⬆️
...ava/org/apache/pulsar/common/naming/TopicName.java	96.09% <100.00%> (+0.03%)	⬆️
...e/pulsar/client/impl/BinaryProtoLookupService.java	83.82% <0.00%> (+1.28%)	⬆️
...g/apache/pulsar/common/lookup/GetTopicsResult.java	88.46% <92.00%> (+25.96%)	⬆️
...a/org/apache/pulsar/client/impl/LookupService.java	80.00% <66.66%> (ø)

... and 368 files with indirect coverage changes