Attempt to rework the review screen to be more useful
Fix indenting and whitespace

because it was the only way to track down the errors..

Use more real estate on xl screens

Prior to this change, on a screem >1200px wide the .container was
capped at 1140px, which leaves a lot of whitespace.

This increases the cap to 1900px, more effectively using
larger screens while still preventing the text from getting so
wide as to be hard to read.

Partial fix for #109

Update jquery version to the full version

datatables uses the fade effect

Restore buttons to review tables

- Switch from dataTable (returns a jquery object) to
DataTable (returns a DataTables API object)
- Update versions of libraries

Doesn't quite work, needs the full version of jquery rather than the
slim version.

Increase initialdelay to 180 seconds.

120 seconds is a little too short; the instance is getting killed partway through coming up.

Add a custom saml_config_loader

* Makes the assumption that we only have one set of keys, and only one
IDP
* If any of the SAML2 variables use relatives paths, these will be
replaced with absolute paths under the current requests's hostname,
port, and scheme

Switch to specifying an SSL flavor

- This helps to ensure that only one is ever set
- But also, because of the way the values are passed in, it's always
going to be evaluated as a string, which is always True. So we can't
just pass in a bool directly

We do need to build images on the dev/2019 branch

These images are later promoted to prod once the commit merges into
the 2019 branch

Always quote numerical branch names

Gitlab-ci expects to see a string; if not quoted this becomes an int.

Don't build review deployment for prod

But do build docs

Don't try to seperate the dev/non-dev image builds

The dev image build uses the prod image build as a base. It doesn't
make sense to seperate them as they need to be sequential, and the
fastest way to do them is to re-use the environment from the first build

Add 2019 prod deploy job

And streamline the names of the other 2019 jobs

Allow EMAIL_USE_SSL to be turned on

LA's mailhost uses implicit-SSL rather than explicit-SSL (STARTTLS) so
we need this available as an option

Align styling for team list on dashboard with rest of dashboard page

Fix #91

Set the correct class for new deployments

to ensure that they get bound to the correct ingress service

Use local file storage for uploads in dev mode

Suplementary file upload already exists if you edit a proposal

Fix #85

Fix notification styling

Fixes #88

Fix TypeError when rendering CSRF failure view

Fix #86

Fix absolute URLs, 'Sydney' on the speaker create form

Fix !87

Add a test fixture which creates a user for testing the CFP

Also add a single proposal which can be reviewed.

Add slug label in more places

This makes it clearer which deploy/service/pod belong together

Set the deployment to use a SHA rather than the SLUG

This will ensure that the deployment gets updated when we deploy