[chore][metric] change log print level for meeting metric already registered

[TyrantLucifer]

change log print level for meeting metric already registered, when user use sql-client executor multi ad-hoc, it will print redundant log, it maybe mislead user.

[luoyuxia]

@TyrantLucifer Thanks for you attention. But register a metric with same name does is not expected, I would like to keep it as warning level. The key point is that the client register the metric with same name for more than once. We shuld fix it from client side. I'm wondering why it'll be register for more than once. Seem when FlussConnection is closed, ConnectionMetricGroup is not closed, so it'll register the same metrics again after init the connection in another query.

[TyrantLucifer]

@TyrantLucifer Thanks for you attention. But register a metric with same name does is not expected, I would like to keep it as warning level. The key point is that the client register the metric with same name for more than once. We shuld fix it from client side. I'm wondering why it'll be register for more than once. Seem when FlussConnection is closed, ConnectionMetricGroup is not closed, so it'll register the same metrics again after init the connection in another query.

Got it. I will try to fix it.