fix: coredump when table name contains '_' and prometheus is enabled

[padmejin]

What problem does this PR solve?

After we enable prometheus(set "perf_counter_sink" to "prometheus"), pegasus ended up core dumped after restart.
We debuged the core, found out it was cored while analysing table name that contains "_".
This PR fixes the bug by changing the order of formating table names.

What is changed and how does it work?

Prometheus does not support some special charactor in metric name.
This original code first formated the table name by replacing special charactor to "" or "@".
Then, it try to parse gpid as prometheus labels by spliting the foramted name by ":" or "".
Unfortunately, tables that already contains "_" may results in unexpected group result, which eventually ended up core.

Checklist

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code

Code changes

• Has exported function/method change
• Has exported variable/fields change
• Has interface methods change
• Has persistent data change

Side effects

• Possible performance regression
• Increased code complexity
• Breaking backward compatibility

Related changes

• Need to cherry-pick to the release branch
• Need to update the documentation
• Need to be included in the release note

[padmejin]

As this picture shows below, when core dumps it was trying to analyze metric naming replica_econ_replica_table_level_RPC_RRDB_RRDB_REMOVE_latency_ns_:impala_historical_profile_p999, where impala_historical_profile is a table we created earlier that contains multiple underscore.

As the code shown below on line 256, it tries to split metrics_name by : first, then split the last part by _ and put the splited tokens in an array that length is 3. Because this table already contains underscore, there are more than 3 tokens, so it got core dumped after at line 259 trying to set the fourth element of the array.

This patch fix it by switching these format order:
Firstly, it try to parse gpid as prometheus labels by spliting the foramted name by : or @.
Then, it formated the table name by replacing special charactor to _ or "@".

In this order tables that contains _ can be parsed expectedly in the first step.

[acelyc111]

LGTM, thanks for your contribution @padme-jin .