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

Turn review jobs back on

Use a new "rego-review" namespace to not interfere with the dev instance.

Add django-crispy-forms for BS4 support

TODO: Remove django-bootstrap-form dependency, left to avoid breaking
other parts.

Disable the review-app jobs for now

They broke the ingress; disabling until that can be sorted out.

Update dev instance deploy script

- We have a flatpages fixture to add in
- Need to let the script exist in the docker context so it can be run

Correct variable name to reflect what it's naming

IT's not the container name, it's the image name. Fix the name to be
less confusing.

Improved handling of static/build and css generation

When the container is mounted, the local contents of . obscure
/app/symposion_app in the image.

Generally speaking, this is handy for development, as it means that
local changes are detected and used immediately without needing to
restart the container.

However, it breaks in the specific case of the sass->css
generation. Prior to this change, the css is generated only after the
first time a page is hit. The generated file is placed in
static/build; however, due to the obscuration, this generated file
isn't visible to the running process.

The next time the container is built, the pre-existing static/build
directory is copied into the container as it's being built; then,
later, that version is what gets served.

This change adds the needed libraries to pre-generate the css as part
of the image build, and runs compilescss to do this, prior to the
collectstatic step.

It also adds a second collectstatic into the make_dev_container
script, so that the visible static/build directory should ahve the
same contents as the obscured static/build directory. It also expands
the .dockerignore file to make sure these files aren't copied into the
image in future.

I'm not sure if this is the right thing to do, as changes to this
directory will be ignored, which could be confusing. Perhaps never
being able to see these generated files is better?