[ISSUE#5697]Add new indicator for core module, especially Jraft and Distro protocal.

[Holdonbei]

What is the purpose of the change

Add new indicator for core module, especially Jraft and Distro protocal.

Brief changelog

1.Remove MetricsMonitor in config module and use MetricsManager to record metrics, which is also do in core and naming module.

2.In order to make MetricsConstant more easier, this pr delete prefix in MetricsConstant.

3.Add Jraft metrics.
Metrics related to Jraft ars below:

• jraft_append_logs_count :the total number of RAFT logs written.
• jraft_replicate_entries_count :the total number of replicate logs from leader to folllower.
• jraft_next_index :the log index that is coping.
• jraft_log_lags :the total numer of delay log.
• jraft_pre_vote_count :the total number of pre vote times.
• jraft_request_vote_count :the total number of request vote times.

4.Add Distro metrics.
Metrics related to Distro ars below:

• distro_verify{resource_type=resourceType, target_server=targetServer, success=true}. It counts verifySuccess times.
• distro_verify{resource_type=resourceType, target_server=targetServer, success=false}. It counts verifyFailed times.
• distro_sync{resource_type=resourceType, target_server=targetServer, success=true}. It counts syncSuccess times.
• distro_sync{resource_type=resourceType, target_server=targetServer, success=false}. It counts syncFailed times.

Verifying this change

Checked.

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

• 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 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 package apache-rat:check findbugs:findbugs -Dmaven.test.skip=true 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.

[haoyann]

LGTM