release-22.1: stats charts on Statement Details page

[maryliag]

Backport 1/1 commits from #82426
Backport 1/1 commits from #82911

cc @cockroachdb/release

---

ui: new charts to statement details page
The overview for a statement details page now
shows charts instead of just the mean value for:

• Execution and Planning Time
• Rows Processed
• Execution Retries
• Execution Count
• Contention

Fixes #74517
Fixes #81153

This commit also introduces mock for matchMedia and canvas
used for testing with jest.

Release note (ui change): Statement Details page now shows charts
for: Execution and Planning Time, Rows Processed, Execution Retries,
Execution Count and Contention.

---

ui: fix contention chart on Statement Details page
This commit adds the proper multiplication factor to
contention value.

It also fixes two small spacing issues.

Release note (bug fix): Use proper multiplying factor to
contention value on Statement Details page.

---

Release justification: high benefit change

[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 

[xinhaoz]

Reviewed 2 of 12 files at r1.
Reviewable status: complete! 0 of 0 LGTMs obtained (waiting on @xinhaoz)