release-22.1: bar chart component and improvements

[maryliag]

Backport 1/1 commits from #80197.
Backport 1/1 commits from #80269.
Backport 1/1 commits from #82321.

/cc https://github.com/orgs/cockroachdb/teams/release

---

ui: move shared graph components to cluster-ui
Part of #74516

This commit moves shared graph functions and components to
cluster-ui package. This is to enable the new bar chart
component to share axes utilities and containers with
the older line graph component in db-console.

Release note: None

---

cluster-ui: create bar graph for time series data
Closes #74516

This commit creates a generic bar chart component in
the cluster-ui package. The component is intended for
use with time series data and should be wrapped in
parent components that convert metrics responses from
the server to the expected format.

Release note: None

---

ui: fixes on bar chart component
This commit:

• Updates z-index of legend, so it doesn't get on top of tooltip
• Fixes the case when there is a single bar (previously not loading)
• Tooltip shows the value with unit
• The tooltip fixes to 1 decimal points when the value is a decimal
• Adds new stories for single bar and chart with scale of Duration
  and Bytes

Release note: None

---

Release justification: high benefit changes

[blathers-crl]

Thanks for opening a backport.

Please check the backport criteria before merging:

• Patches should only be created for serious issues or test-only changes.
• Patches should not break backwards-compatibility.
• Patches should change as little code as possible.
• Patches should not change on-disk formats or node communication protocols.
• Patches should not add new functionality.
• Patches must not add, edit, or otherwise modify cluster versions; or add version gates.

If some of the basic criteria cannot be satisfied, ensure that the exceptional criteria are satisfied within.

• There is a high priority need for the functionality that cannot wait until the next release and is difficult to address in another way.
• The new functionality is additive-only and only runs for clusters which have specifically “opted in” to it (e.g. by a cluster setting).
• New code is protected by a conditional check that is trivial to verify and ensures that it only runs for opt-in clusters.
• The PM and TL on the team that owns the changed code have signed off that the change obeys the above rules.

Add a brief release justification to the body of your PR to justify this backport.

Some other things to consider:

• What did we do to ensure that a user that doesn’t know & care about this backport, has no idea that it happened?
• Will this work in a cluster of mixed patch versions? Did we test that?
• If a user upgrades a patch version, uses this feature, and then downgrades, what happens?

[cockroach-teamcity]

This change is