ui: Fixes for various small UI bugs

[mrtracy]

A grab bag of various micro-fixes, each closing a github issue.

Fixes #12658

The custom time range displayed in the top bar on the cluster overview page is
currently displaying times in the local time zone, which does not match the
ticks on graphs. This change converts it to display in UTC.

Fixes #12997

Disables the "searchable" option on our dropdowns to prevent the blinking-cursor
effect. This option is not necessary for dropdowns at our current cluster sizes,
and the "search" mode of dropdowns has not been styled, so we simply disable to
search option.

Fixes #13002

Axis on "Capacity" graph is now properly labeled with Byte units.

---

This change is 

[tamird]

typo in commit message "disable to search option" - i think you meant "the".

---

Reviewed 4 of 4 files at r1.
Review status: all files reviewed at latest revision, 1 unresolved discussion.

---

pkg/ui/app/containers/timescale.tsx, line 28 at r1 (raw file):

class TimeRange extends React.Component<TimeRangeProps, {}> {
  render() {
    let s = this.props.start.clone().utc();

why does this need to clone?

---

Comments from Reviewable

[mrtracy]

Fixed the commit message typo.

---

Review status: all files reviewed at latest revision, 1 unresolved discussion.

---

pkg/ui/app/containers/timescale.tsx, line 28 at r1 (raw file):

Previously, tamird (Tamir Duberstein) wrote…

why does this need to clone?

Because moment.js is a fairly outdated library, and utc(), or any function that changes the display timezone, and in fact most methods in this library mutate the original object.

The have been aware of this since 2014: moment/moment#1754

They are hesitant to make it immutable because it would so radically break backwards compatibility; however, nobody else has stepped up to the plate and created an immutable version.

As of now, using "clone()" all over the place is the only way to get sane behavior.

---

Comments from Reviewable