feat: export runtime metric to promethues

[SSebo]

I hereby agree to the terms of the GreptimeDB CLA

What's changed and what's your intention?

export tokio runtime metrics

Please explain IN DETAIL what the changes are in this PR and why they are needed:

• use tokio-metric to collect runtime metrics
• use tokio-metric-collector to expose to promethues

Checklist

• I have added the necessary unit tests and integration tests.

Refer to a related PR or issue link (optional)

close #1529

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (06fd7fd) 85.87% compared to head (fb73057) 85.24%.
Report is 7 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #2985      +/-   ##
===========================================
- Coverage    85.87%   85.24%   -0.63%     
===========================================
  Files          780      783       +3     
  Lines       126184   126638     +454     
===========================================
- Hits        108356   107954     -402     
- Misses       17828    18684     +856     

[SSebo]

@MichaelScofield PTAL

[MichaelScofield]

@SSebo can you attach some output as an example to illustrate the tokio runtime metrics look like?

[fengys1996]

LGTM, Thank you @SSebo .

[waynexia]

Others LGTM

[killme2008]

Have to sort the deps.

[SSebo]

@SSebo can you attach some output as an example to illustrate the tokio runtime metrics look like?

Of course. How about this ?

            assert!(metric_text.contains("runtime_0_tokio_budget_forced_yield_count 0"));
            assert!(metric_text.contains("runtime_0_tokio_injection_queue_depth 0"));
            assert!(metric_text.contains("runtime_0_tokio_workers_count 5"));