Create a group for the RAVEN pipeline, add users, and give the group
specific permissions. Right now, they are just allowed to populate
the Fermi, SNEWS, and Swift pipelines for uploading external events.

Too many users are complaining about not receiving phone or email
alerts. I need to know when the relevant contacts and notifications
were created, updated, verified, etc. so I can confirm or deny that
they had configured things correctly.

Certain filters are being moved out of the djangorestframework
package and into djangorestframework-guardian.

The previous method is removed in Django 2.0 and is causing
all kinds of warnings in testing with pytest.

with --ignore calls

Co-authored-by: Tanner Prestegard <tanner.prestegard@ligo.org>

mainly to mock out getting the internal phone number list

Email alerts seem to be more problematic due to AWS SES rate
limiting and phone alerts are more important, so we should send
phone alerts first.

Addition to 058fd28d.

Discovered that AJAX requests to the API from the web view were
using certificates in people's browsers even if they were logged
out of the Django session.  So when they wanted to view the page
as a public user they still saw some extra information.

No security risk since they needed to have a valid certificate
anyway, but a bit annoying.

We've had some bad cases where a log entry is created, but the
file is not saved due to filesystem errors. So we put the file
creation in a try-except block and if it fails, delete the log
message that was just created before re-raising the exception.

Previous arrangement was not including zero-valued fields. We now
include all non-None fields.

Due to the fact that we are using multiple attribute authorities,
there are some cases (specifically email) where there are multiple
values provides for an attribute, separated by a semi-colon.

This update handles those instances and takes the first value in
the list.

Instead of looping over EmailMessage.send() calls, we now get the
email backend and send a list of messages. Note that the backend
sends the messages individually still but this cuts out some of the
overhead.