New default: don't mount the local code repo into the container -
non-developers just want a stable image (probably a tag of the code)
to test against. Instead, make the volume mount an option that
GraceDB developers can add, in order to facilitate development.

This is only really relevant for dev servers when we are
re-populating the database, and for local development with
a Docker container.

This image will be for developing locally on your own laptop.

By default, login will use Shibboleth.  But there is a new
settings variable (USE_SHIBBOLETH_LOGIN) which, if False,
will instead activate password-based login, which is best
for development on a laptop or such.

This will be useful since we plan to build multiple images for
various purposes. So, we create a new directory, docker/,
which will have a subdirectory for the configuration for each image.

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.

Update base.py: updating the version number to "2.7.1-1". There's no functional differences, just a few settings for the new AWS deployment. I'm also adding the "*-1" qualifier so that I and users can tell that the new AWS deployment is in place and working.