Naming fix.
Use PostgreSQL in CI.
A commentary on software engineering.

Also, extend Capybara wait time in CI.
We need to assign the Bcdatabase.load result to use it.
GET /api/v1/data and associated client-side binding.

I have chosen to separate a search record from its result set for the
following reasons:

1. Conceptually, there's a has-many relationship between the two, and
   the API is designed to expose only the most recently completed
   search.

2. We currently do not need to convert result sets into arrays of
   Ember.Objects: we're just displaying that data in SlickGrid and
   SlickGrid can operate just fine on Javascript arrays and objects.
   This means that we can treat the result set more like a (large)
   value.
Update Cases mock to match latest event API schema.
Spike out the event search results grid.
Don't start Sidekiq as part of app infrastructure.

When Sidekiq is running in test, we end up with a connection to the
app's test database, and this is incompatible the test reset code done
by Rails.
We run an app server in test, too.
Use Sidekiq inline testing in test.

Rationale: Requiring sidekiq/testing in our Cucumber harness does us no
good when the app server is a separate process.
Merge branch 'view-search-results'

Conflicts:
	ci-exec.sh
	config/database.yml