Don't override LVALERT_OVERSEER_INSTANCE settings from
envrionment variables.

1) Fixed a 500 Internal Server error when removing labels from events
   that do not exist. Basically the ValueError.message method was
   depreciated in python3; replaced it with a str(error).
2) Bumped version to 2.8.0

Fixed LVAlert server for "test" container, and fixed 500 server error
when sorting p_astro list for the public event page. I think this

https://stackoverflow.com/questions/27776026/lambda-arguments-unpack-error

fixes it.

Reflects new usage of EM_READY and EM_Selected labels in
superevent 2.0.

The server will now return a 400 "bad request" error for RAVEN
createVOEvent calls if:
  1. em_type for the associated superevent is None
  2. em_type for the associated superevent is not a valid graceid
  3. the event associated with em_type cannot be found
  4. the combined_skymap_filename is set, but the file could not
     be found.

Merge branch 'python3' of https://git.ligo.org/lscsoft/gracedb into HEAD

For some reason, django makemigration wasn't recognizing that the
voevent ivorn table actually existed, so it was trying to recreate
that table and the pytests were running into an issue.

Yeah, save it.

API requests on AWS were returning a 500 Server Error, traced it
down to a bytes vs string conversion when retrieving the certificate
subject

New certificates for nagios, gstlalcbc, and detchar

Merging in configuration changes from the AWS deployments in
order to test python3 in AWS.

Neglecting to create and apply the voevents migration to the 'events'
model would cause gracedb's tests to fail.

Squashing errors in the gitlab pipeline.

Adding a javascript 'confirm' dialog box that comes up before
exposing/hiding superevents from the public.

I think when I inadvertently removed the 0005-* automatic migration
that broke the tests and subsequent migrations. I'm putting everything
back into place in a form athat should restore the tests.

There were some copy/paste errors that I cleaned up. Interestingly though,
voeventlib-parse will just do crazy things with the xml nesting instead
of throwing an error.