[Improve]Optimize the collection of metrics for TubeMQ

[gosonzhang]

Description

The parent issue is: #2173

The current implementation of metric is not good enough, mainly because the structure used is still the content in the form of Atomxxx, this can be replaced by the xxxAdder structure; and then the collected content can be a little more, which is convenient for problem location and analysis.

This issue tracks improvements to this area

• [TubeMQ] Abstract metrics' interface #2433
• [TubeMQ] Add Gauge and Counter implementation classes #2445
• [TubeMQ] Add Histogram implementation classes #2451
• [TubeMQ] Adjust the statistics of Broker's message service part #2474
• [TubeMQ] Optimize GroupCountService logic implementation #2478
• [TubeMQ] Add WebCallStatsHolder class for Web API call statistics #2480
• [TubeMQ]Optimize MsgMemStatisInfo implementation logic #2484
• [TubeMQ] Optimize MsgFileStatisInfo implementation logic #2488
• [TubeMQ] Add MsgStoreStatsHolder class #2505
• [TubeMQ] Add Broker metric operation APIs #2508
• [TubeMQ] Optimize Broker's JMX metric interface #2516
• [TubeMQ] Adjust the statistical logic of the Master service status #2517
• [TubeMQ] Adjust the client's metric statistics logic #2518
• [TubeMQ] Add Master metric operation APIs #2552
• [TubeMQ] Remove obsolete metric codes #2603
• [TubeMQ] Optimize the content of statistical metrics #2728

[gosonzhang]

This part has come to an end for the time being, and then we will improve the content of the document