ui: show metric on charts tooltip

[maryliag]

To make it easier to identify the metric being used to generate charts, this commit adds the metric to the tooltip of all charts on the Metrics page.

Fixes #109277

This also fix the metric name for Schema Registry Registrations.

Fixes #108095

Release note (ui change): On the Metric page, now the information about which metric is used to create each chart is available on the chart's tooltip.

Release note (bug fix): Fix metric name for Schema Registry Registrations.

[cockroach-teamcity]

This change is 

[koorosh]

Reviewed all commit messages.
Reviewable status: complete! 0 of 0 LGTMs obtained (waiting on @maryliag)

a discussion (no related file):
I have concern about manual updating tooltips to match provided metric names.
Metric name is already provided to component so it can be reused.
I would suggest something like this:

• extend props with if showMetricsInTooltip bool prop;
• add following logic to InternalLineGraph#render method:

render() {
    const {
      title,
      subtitle,
      data,
      tenantSource,
      preCalcGraphSize,
      legendAsTooltip,
      showMetricsInTooltip,
    } = this.props;
    let tooltip = this.props.tooltip;
    // Extend tooltip to include metrics names
    if showMetricsInTooltip {
      if (this.metrics.length == 1) {
        tooltip = (
          <>
            {tooltip}
            <br />
            <br />
            Metrics: {this.metrics[0].name}
          </>
        )
      } else {
        tooltip = (
          <>
            {tooltip}
            <br />
            <br />
            Metrics:
            <ul>
              {this.metrics.map(m => (<li key={m.name}>{m.name}</li>))}
            </ul>
          </>
        )
      }
    }
    ...

---

[koorosh]

Reviewed 1 of 14 files at r1, 14 of 14 files at r2, all commit messages.
Reviewable status: complete! 1 of 0 LGTMs obtained (waiting on @maryliag)

[maryliag]

bors r+

[craig]

Build failed:

• Bazel Essential CI (Cockroach)

[maryliag]

bors r+

[craig]

Build succeeded:

• Bazel Essential CI (Cockroach)

[blathers-crl]

Encountered an error creating backports. Some common things that can go wrong:

1. The backport branch might have already existed.
2. There was a merge conflict.
3. The backport branch contained merge commits.

You might need to create your backport manually using the backport tool.

---

error creating merge commit from 3803d12 to blathers/backport-release-23.1-111469: POST https://api.github.com/repos/cockroachdb/cockroach/merges: 409 Merge conflict []

you may need to manually resolve merge conflicts with the backport tool.

Backport to branch 23.1.x failed. See errors above.

---

_{🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.}