This includes debouncing user input, querying, and some style stuff.

They'll be added back when we figure out how to implement the artists view.

There are two sources of updates for the search input.

1. The user typing directly into the input. This change comes from a
child of the state container.

2. The url changing. This comes from the parent of the state container.

There are a few ways to reconcile props from multiple locations, none of
which work well.

1. Use key to render a new component when the query changes. This works
but the focus of the input is lost.

2. Use componentDidUpdate. It is intended for props and causes an extra
render.

Updates flow up from the input to the StateContainer and to the url.
State flows down from the url and the state container to the
presentational components.

This is clear and simple. I think the StateContainer should be simpler.

They both independently handle fetching and rendering of each section of
the search page.