[ROCKETMQ-312] Use independent thread pool for QueryMessageProcessor

[zhouxinyu]

What is the purpose of the change

Resolve issue ROCKETMQ-312.

QueryMessageProcessor and PullMessageProcessor are sharing the same thread pool, should split it.

Brief changelog

Add a query message executor to accept and handle QUERY_MESSAGE and VIEW_MESSAGE_BY_ID requests.

Verifying this change

Start the server, and submit some query message requests, then verify the functionality. Also
the logger RocketmqWaterMark will trace the capacity info of the related queue.

Follow this checklist to help us incorporate your contribution quickly and easily:

• Make sure there is a JIRA issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA 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 [ROCKETMQ-XXX] 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 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.

[coveralls]

Coverage decreased (-0.02%) to 39.128% when pulling 717117b on zhouxinyu:ROCKETMQ-312 into cba3089 on apache:develop.

[shroman]

Makes sense. +1

[vsair]

LGTM

[vongosling]

+1

[zhouxinyu]

Merged!