Fix mysql.innodb.row_lock_time metric unit

[rashiq]

What does this PR do?

Changing the unit and description of mysql.innodb.row_lock_time.

Motivation

The metric is ingested based on this status variable. It's in miliseconds and collects the total time spent on acquiring row locks.

Review checklist (to be filled by reviewers)

• Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
• Add the qa/skip-qa label if the PR doesn't need to be tested during QA.
• If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 87.06%. Comparing base (846abd9) to head (a7973a3).
Report is 8 commits behind head on master.

Additional details and impacted files

Flag	Coverage Δ
activemq	?
cassandra	?
hive	?
hivemq	?
ignite	?
jboss_wildfly	?
kafka	?
mysql	89.54% <ø> (-0.01%)	⬇️
presto	?
solr	?

Flags with carried forward coverage won't be shown. Click here to find out more.

---- 🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests
• JS Bundle Analysis - Avoid shipping oversized bundles

[rashiq]

Hi @lu-zhengda! Thank you for your review. It tells me it still needs a review from someone from the DataDog/agent-integrations team. Is there someone I can request a review from?

[lu-zhengda]

Hi @rashiq, thanks for submitting the fix. You are good on the review. I will merge the PR shortly.