release-23.1: ui: introduce foundations to support configurable timezone display

[blathers-crl]

Backport 1/1 commits from #99848 on behalf of @zachlite.

/cc @cockroachdb/release

---

This commit adds the foundational dependencies and components needed to display timestamps in DB console in a user's preferred timezone.

Introduced:

• A dependency on moment-timezone in DB console and Cluster UI.
• A cluster setting: ui.display_timezone.
• A timezone context with a default value of "UTC". This enables backwards-compatability for cluster-ui components. No changes in cloud are needed, and cluster-ui components will continue to display timestamps in UTC.
• A context provider at the top of DB console's component tree.

Part of: #40419
Epic: https://cockroachlabs.atlassian.net/browse/CRDB-24406
Release note: None

---

Release justification: to unblock delivery of successful GA

[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 

[maryliag]

Reviewable status: complete! 1 of 0 LGTMs obtained (waiting on @sjbarag, @xinhaoz, and @zachlite)