Enter QA environment with basic search/browse functionality

Configure Solr
Add IndexService library
Index and delete sample data with rake task
Generate catalog controller to customize blacklight
Show search results in catalog home view
Basic keyword search
Refine search with facets
Show basic metadata for single record

To test in your browser:  Follow the new README instructions to configure and start the dummy application, and index sample data to Solr.  You may need to visit [http://127.0.0.1:8983/solr/#/~cores/blacklight-core](http://127.0.0.1:8983/solr/#/~cores/blacklight-core) and click `Reload` for the sample data to index. Go to [http://localhost:3000/catalog](http://localhost:3000/catalog) (you will see the same page if you go to http://localhost:3000 because of the current route configuration).  You should see your sample record.  You should be able to search and refine your search with facets.  You should also be able to view some basic metadata for a single record if you click on the record id.  

There are also two unit test you can run with `bundle exec rake ci`.

Because we are likely moving away from Solr, I focused on getting Solr working without necessarily employing the most elegant solutions.  

In `schema.xml`, everything above line 476 `<fields>` is standard.  Everything below is ours, with the exception of `dynamic field definitions`, which is also standard.
I'd like to see this fixture replaced with a factory.  Then the sample data loader could build out an arbitrary number of objects.

I know of two potential blockers to doing this:
  - `dpla-map` models don't yet know their JSON-LD context, so generating good MAP json from the existing factories is a little bit complicated. See: https://gist.github.com/no-reply/f425057a660ae910a239#comment-1324050
  - `dpla/map/factories` doesn't yet do sequences, so building multiple objects will build them all with the same data. See: https://github.com/thoughtbot/factory_girl/blob/master/GETTING_STARTED.md#sequences

Is this something we want to pursue as part of this PR? I'm not sure either of the blockers above really need to be dealt with to duplicate current behavior, and it seems important to get our test data from the models, rather than maintaining manually.