LCA2022 Setup

Update dates and descriptions for LCA2022.
Remove old miniconf proposal types.
Add local timezone to speaker profile.

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

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.

Disable the review-app jobs for now

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

Test sphinx generation on every commit

Produces a downloadable artifact

Revert "Split out dev/prod docker builds into parallel jobs."

This reverts commit d7065ee43d31f55b1ad9860d3cb5e1cbdb747e73.

Dev build re-uses prod build, so they can't be split (and dev build
won't take much extra time anyway)

Fix container name reference for deploy command

In the pod, the container is not called frontend

Build an ephemeral dev container for rego testing

Create a ephemeral dev container to facilitate testing of
populate_inventory. It can be created, tweeked in the admin interface,
files updated in admin's populate_inventory, then redeployed to deal
with those changes.

A branch based one will need to be created to so we can do this work
without polluting the master branch.

Improve image update workflow

This improves the administrative workflow of deploying updated images to
the k8s cluster. Still tag latest however, as that's important to
old-workflow.

Would be good to block this and have it fail on a db migration so it
doesn't happen accidently, and make the deployer deal with it.

Lets try to automate this build a bit

This doesn't rebuild on subproject changes... this is something that
will need fixed.