Instantiating a second version for the API.  For now, it's identical
to v1, but can be customized as needed in the future.

Moving a few base class throttles and fields from the events app up
one level so that they can be used elsewhere.

Moved events.api and superevents.api into the new api app.
We want to have a versioned API, so these are now in
api.v1.events and api.v1.superevents, respectively. Part of this
change is that we require a custom reverse function (api_reverse)
for handling versioning. Much of the required code changes for this
migration include converting reverses to use this function and
changing relative imports appropriately.

Added utility functions for hiding and exposing logs from
LV-EM and the public. They are triggered by log messages being
tagged or untagged.

Also added utilities for hiding/exposing superevents.

New custom model backend, which includes the table/object
permissions backend and does not authenticate.

New /latest/ page includes events and superevents. We also
move the old events 'latest' page to /events/latest/, changed the
view name, and fixed reverses to that page appropriately.

Activate Django sites app and create a migration which adds the
LIGO.ORG domain name of the GraceDB instance as a Site. This will
be used to build absolute URIs without needed a request object.

Instantiating a new alerts app and moving the alert functionality from
events/alert.py to alerts/old_alert.py. This commit forms a starting
point where the old alert functionality is still in place and we can
rework the alert infrastructure to be more modularized, flexible,
and adapted to superevents.

Renaming LIB -> oLIB and gstlal-spiir -> spiir, at the request of
the pipelines.

django-extensions was just in the test settings before (i.e., not
deployed on production), but it is pretty nice and useful, so we
are moving it into the base settings so that it can be used
everywhere!

Adding middleware which checks the client version (for everything
under /api*) by using the User-Agent header. Obviously requires the
client to set the header appropriately as well.  Allows access
when the header is set but 'gracedb-client' is not found in it
since browsers have to access the web browsable API.

Unsure why messaging app was not enabled; it's needed for
posting flash messages about contacts and notifications.