chore(deps): update all dependencies

See merge request !110

chore(CHANGELOG): update after bumping requirements

See merge request !109

chore(deps): update all dependencies

See merge request !107

fix(tox): add missing copier-templates-extensions dependency

See merge request !106

chore(CHANGELOG): record that renovate now manages deps

See merge request !105

fix(template-devops-requirements): tweak index-url for renovatebot

See merge request !104

Renovatebot *should* understand `--index-url` in `requirements.txt`
files but the renovatebot docs[1] explicitly call out that it needs to
be the first line. Our files have it as the first *effective* line after
comments but, to be pedantic, it's not the first *physical* line. Update
the `--index-url` usage to match the renovatebot docs.

[1] https://docs.renovatebot.com/python/#index-url-in-requirementstxt

feat: template minimum version numbers for dependencies

See merge request !103

In #98 some of the challenges with having renovate keep dependencies
fresh in this repo were discussed. In particular the contents of the
template/ directory are, well, templated and so there's no guarantee
that renovatebot will be able to parse them. Even if we made them
parseable, it's hard to enforce continued parse-ability in CI.

Instead, lean in to the templating approach by adding files which
renovatebot *can* parse specify the minimum version requirements and
have copier read from that file to populate the requirements within the
template.

Fortunately the copier installed alongside renovatebot has support for
copier-templates-extensions installed which, in turn, allows adding
custom extensions to the template context via Python scripts inside the
template repo.

Combine both things together: we now have `template*requirements.txt`
files which renovatebot *can* parse and update which are used to
replace constructions such as `{{ deps.somepackagename.version }}` in
the `pyproject.toml` and `.gitlab/webapp.gitlab-ci.yml` files. When
renovatebot updates the `template*requirements.txt` files, the templates
will automatically make use of the new minimum versions.

Note that these are always *minimum* versions. We don't want to stop
renovate from being able to _additionally_ update dependencies in
templated repos even if a new version of the template with bumped
dependencies hasn't been released.

Add some configuration to `renovate.json` to reduce the number of MRs
likely to be raised by renovate to a manageable rate.

[1] https://github.com/renovatebot/renovate/discussions/34368

docs(template): add LICENSE to template and other cleanup

See merge request !102

chore(ci): remove redundant release-it import

See merge request !101

feat: add debugpy to development images

Closes #106

See merge request !100

Add in the debugpy configuration which has somehow got lost along the
way. The debugpy port is already exposed in docker-compose.yaml and so
this config was always _meant_ to be in the development image but seems
never to have been added.

This unblocks support for debugging running images in IDEs such as VS
Code.

Closes #106

chore(deps): update dependency uis/devops/continuous-delivery/ci-templates to v6

See merge request !90

feat: add auto-built documentation

See merge request !99

Add base scaffolding to allow auto-generated documentation. Take the
opportunity to bump the CI template versions.

feat: change gunicorn worker settings to match GCP recommendation

See merge request !80

feat: bump CI template versions

See merge request !98

fix(copier): allow updating templates without git or poetry

See merge request !97

When running in the context of renovatebot, copier does not have poetry
or git commands available so don't try running them.

Plumb in positional args from the tox task to pytest

See merge request !96

fix: explicitly install poetry-plugin-export

Closes #103

See merge request !95