[ISSUE #19]Message track query enhancement

[zhangjidi2016]

What is the purpose of the change

#19

Brief changelog

XX

Verifying this change

XXXX

Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

• Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
• Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
• Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
• Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test to make sure integration-test pass.
• If this contribution is large, please file an Apache Individual Contributor License Agreement.

[StyleTang]

Great, this feature helps users who use custom track message topic to query message trace. 👍
I have several comments here.

1. message track topic should have a default value, after this PR, each user will need at least 3 clicks when making a query message trace query (even if they use the default message track topic).
2. I suggest that the message track topic should be in the message trace page but not in MsgTraceDetailDialog, and the browser can cache which topic was chosen before.
3. rocketmq.config.msgTrackTopicName is useless, we can just remove it.

[StyleTang]

Is traceTopic must have? maybe we can use the default value if use don't choose the topic.

@RequestParam String traceTopic

[zhangjidi2016]

TraceTopic can be empty and system topic (RMQ_SYS_TRACE_TOPIC) is used by default.

[StyleTang]

1. What will happen if both skipSysProcess and skipRetryAndDlq are true.
2. maybe we can handle skipSysProcess and skipRetryAndDlq together, for example use Java lambda stream.

allTopics.getTopicList().stream().map((item)->{
                ...
            }).filter(new Predicate<String>() {
                @Override
                public boolean apply(@Nullable String input) {
                    ...
                }
            }).collect(Collectors.toSet());

[zhangjidi2016]

Yes, need to take into account the fact that both skipSysProcess and skipRetryAndDlq are true，I will optimize this method using stream.

[StyleTang]

In my point of view, I don't suggest putting the topic selection on the popover. It’s more appropriate to put it on the page.
If we put it on the message trace page, for most users who use the default message track topic, they can just ignore it, but on the popover, the unnecessary click is required.

I suggest something like below

[StyleTang]

Trivial. (and it is not introduced by this PR, I'm OK to merge it)
can just use

allTopics.setTopicList(topics);

[StyleTang]

👍
It’s great to delete useless system topics