[ISSUE #7534]use a new class to replace topiclist in concurrent scene

[keranbingaa]

fix #7534

[codecov-commenter]

Codecov Report

Attention: 10 lines in your changes are missing coverage. Please review.

Comparison is base (1be5ebc) 43.11% compared to head (fa17940) 43.10%.
Report is 1 commits behind head on develop.

Files	Patch %	Lines
...mq/remoting/protocol/body/ConcurrentTopicList.java	0.00%	8 Missing ⚠️
...che/rocketmq/remoting/protocol/body/TopicList.java	0.00%	1 Missing ⚠️
...he/rocketmq/tools/admin/DefaultMQAdminExtImpl.java	0.00%	1 Missing ⚠️

Additional details and impacted files

@@              Coverage Diff              @@
##             develop    #7559      +/-   ##
=============================================
- Coverage      43.11%   43.10%   -0.02%     
- Complexity      9708     9710       +2     
=============================================
  Files           1159     1160       +1     
  Lines          84035    84043       +8     
  Branches       10922    10922              
=============================================
- Hits           36234    36226       -8     
- Misses         43294    43304      +10     
- Partials        4507     4513       +6     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[joeCarf]

这个类似乎与之前的TopicList完全一致，有什么区别吗

[keranbingaa]

目前问题是原来的TopicList中改成CopyOnWriteArraySet后，在某些接口调用时，如果topic数很大会有超时的问题，但如果用原来的HashSet则不会有这个问题，新增的需要并发修改的接口则用新增的ConcurrentTopicList这个类，避免并发修改的异常，通过这种方式把两类接口区分开

[lizhimins]

如何判断是这里慢而不是 config json flush 慢呢

[keranbingaa]

增加了一个单元测试证明两个类在add huge topiclist时效率的差异

[lizhanhui]

Need metrics to verify this pull request is actually fixing the attempted bottleneck.