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. 

Using docker secrets if present to populate the sensitive environment
variables whose values we do not want in clear text in the repo
amend: fixed typo

added em_type and coinc_far to api requests. next step: modify client to update these fields, make sure logging and alerts are active, and then modify tests.

    - 0052_update_gstlalcbc_O3b_cert.py: gstlalcbc was issued a new cert at CIT.
      I manually migrated on production and playground, but i'm backing up the
      migration here.
    - 0005_add_coinc_far_and_em_type.py: snapshotting the migration for the new
      `em_coinc` and `em_type` data fields. This will most likely change.