Epic: Dashboard Performance

Make components Pure or Memorize them
Background
Components can often needlessly re-render when receiving the same props due to how react does comparisons between previous props and next props. Making class components PureComponent or wrapping function components in React.Memo can solve this problem for components that re-render frequently but have props that don't change Frequently

Potential Components:
NavHeader
InnerView (inside visualization/components/View.tsx)

----

Handle Unnecessary Prop Changes

Background
Components can rerender unnecessarily when they are passed the same props but React computes them to be different due to how react computes prop changes. The majority of the components in the app that re-render are called but unnecessary prop changes. These might be caused by things like using anonymous functions, or by creating a new style object in a render loop. See [this explanation](https://medium.com/welldone-software/why-did-you-render-mr-big-pure-react-component-part-2-common-fixing-scenarios-667bfdec2e0f) from the WhyDidYouRender library.

Components to investigate
OverlayController
TypeAheadDropDown
DashboardRoute
TimeRangeDropdown

----

Related to unnecessary re-renders
In case this is helpful, here's how I solved a similar issue in notebooks & data explorer in regards to the functions panel: https://github.com/influxdata/ui/pull/1959.

----

"Create a query. Go on!" rendered while waiting to render a dashboard on a slow machine

Steps to reproduce:
List the minimal actions needed to reproduce the behavior.

macos + chrome
very heavily loaded laptop
refresh an existing dashboard
Expected behavior:

See a dashboard or at least see a spinner or an error message.

Actual behavior:

Create a query. Go on!

After a while when the browser manages to get some CPU cycles it finally renders the dashboard.

Environment info:

System info: Darwin 20.6.0 x86_64
InfluxDB version: us-west1-1.gcp.cloud2.influxdata.com