fix: remove length validation for 'secret_id' variable

See merge request !20

feat: add length validation for 'secret_id' variable

See merge request !19

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

See merge request !18

See merge request !17

update CI templates versions

See merge request !16

feat: module should constrain only the minimum required provider version

See merge request !15

fix(gitlab-ci): re-enable check_latest_tag_in_changelog job

See merge request !14

fix(gitlab-ci): disable check_latest_tag_in_changelog job

See merge request !13

The "check_latest_tag_in_changelog" job is useful if releases are being
manually managed but in the world of release-it, it's unnecessary.

This wouldn't be a problem except that the current check [1] doesn't
like release-it's changelog.

[1] https://gitlab.developers.cam.ac.uk/uis/devops/continuous-delivery/
  ci-templates/-/blob/master/auto-devops/
  check-latest-tag-in-changelog.yml?ref_type=heads#L17

feat: add automated release management

Closes #10

See merge request !11

How we version and develop modules is something which needs documenting
beyond individual READMEs. For example, [1] covers how hotfixes should
be made.

[1] http://tinyurl.com/yskndvdu, or:
  https://guidebook.devops.uis.cam.ac.uk/en/latest/tutorials/
    automating-gitlab-releases/
    #creating-a-hotfix-for-a-previously-released-version

The release-it utility expects the CHANGELOG to not have extra text at
the top. Make it so.

Automated release management essentially requires conventional commits
to be used. Add the commitlint job to enforce this.

Following instructions from the guidebook, enable release automation for
this module.

feat: allow specifying IAM bindings via iam_policy variable

Closes #11

See merge request !12

Rather than requiring `project` and `region` be set, default to using
the project and region of the Google provider.

Add a new variable, `iam_policy`, which allows one to map a set of IAM
roles to assigned members. This has been ported from a MR for GitLab
Project Factory[1].

[1] https://gitlab.developers.cam.ac.uk/uis/devops/infra/gitlab-project-factory/-/merge_requests/51

feat(README): reflect use of packaged terraform module

Closes #9

See merge request !10

We now publish this module via a terraform registry managed within
GitLab. Update README and examples to reflect this.

Closes #9

fix: Terraform errors when bootstrapping projects

Closes #8

See merge request !9

Add a `manage_secret_versions` variable for enabling/disabling the managing of
secret versions/payloads.

Update example in the README of how to create a secret manager that doesn't
manage versions.

Refs: #8

ci: publish to GitLab Terraform registry when tagged with valid semver

Closes #7

See merge request !8