This commit will make a few changes. The
orginal version of the semantic checking
function was a bit more difficult to read.
It is now somewhat easier to follow how
the regex is structured. Also the function
has been renamed to check_python_version
since it has 2 functions, making sure that
the version is semantically correct and the
second is to make sure that it is installed
on the user's machine. This makes it easier
to follow the logic for the flags, -p or
--python-version and -l or --list-versions

This commit will make a few changes. The
orginal version of the semantic checking
function was a bit more difficult to read.
It is now somewhat easier to follow how
the regex is structured. Also the function
has been renamed to check_python_version
since it has 2 functions, making sure that
the version is semantically correct and the
second is to make sure that it is installed
on the user's machine. This makes it easier
to follow the logic for the flags, -p or
--python-version and -l or --list-versions

…ttps://github.com/cisagov/skeleton-generic into improvement/correct-semantic-python-version-checks

Co-authored-by: dav3r <[email protected]>

Co-authored-by: dav3r <[email protected]>

Add the `check-useless-excludes` meta hook to verify that any defined
`exclude` directives apply to at least one file in the repository.

Instead of manually installing Packer we can instead leverage the
hashicorp/setup-packer Action just as we do for Terraform.

He is no longer a member of @cisagov/vm-dev.

Previously we only provided a lower bound for the version, but pinning to a specific version aligns with what has been done with the prettier hook and how pre-commit hooks are pinned in general.

The flake8-docstrings package is rarely updated, so there is no real downside to pinning to a specific version.

Co-authored-by: Nick <[email protected]>

Bumps [actions/cache](https://github.com/actions/cache) from 3 to 4.
- [Release notes](https://github.com/actions/cache/releases)
- [Changelog](https://github.com/actions/cache/blob/main/RELEASES.md)
- [Commits](actions/cache@v3...v4)

---
updated-dependencies:
- dependency-name: actions/cache
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>

Bumps [crazy-max/ghaction-github-status](https://github.com/crazy-max/ghaction-github-status) from 3 to 4.
- [Release notes](https://github.com/crazy-max/ghaction-github-status/releases)
- [Commits](crazy-max/ghaction-github-status@v3...v4)

---
updated-dependencies:
- dependency-name: crazy-max/ghaction-github-status
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>

This is done automatically with the `pre-commit autoupdate` command.
The pre-commit/mirrors-prettier hook was manually held back because the
latest tags are for alpha releases of the next major version.

Use the latest v3 release available from NPM.

…max/ghaction-github-status-4

Bump crazy-max/ghaction-github-status from 3 to 4

…s/cache-4

Bump actions/cache from 3 to 4

Use an Action to install Packer in our GitHub Actions workflows

…hon-version-checks

Add checks for correct semantic version of Python

Remove @jasonodoom as a codeowner

The pip-audit tool will audit any supplied pip requirements files for
vulnerable packages.

…hook

Add the `check-useless-excludes` hook to the pre-commit configuration

…mmit_hook

Add a pre-commit hook to run `pip-audit`

Add a lower-bound pin for the `flake8-docstrings` `pip` package

Update `pre-commit` hooks

This replaces the now archived pre-commit/mirrors-prettier hook.

Switch the `pre-commit` hook used to run `prettier`

Add a `workflow_dispatch` trigger so we can manually run the workflow
if needed.

This means that we need not worry about whether variables are
explicitly specified as null.  Since this is not something we were
expecting, it makes sense to avoid the situation.

See also:
https://developer.hashicorp.com/terraform/language/values/variables#disallowing-null-input-values

Version 1.1 of Terraform is the first version to support the nullable
key in variable definitions.

Also update the comment associated with this line to something a bit
more truthful, since we are using 1.5.7 in
cisagov/setup-env-github-action.

Co-authored-by: David Redmin <[email protected]>

Co-authored-by: David Harris <[email protected]>

Co-authored-by: David Harris <[email protected]>

This Action will provide information about the usage of GITHUB_TOKEN in
the workflow. It should be added to _every_ job in _any_ workflow to
provide information for analysis.

This changes the default permissions for the GITHUB_TOKEN used in our
GitHub Actions configuration to the minimum required to successfully
run.

This is done automatically with the `pre-commit autoupdate` command.

Ensure that all hook ids are sorted alphabetically in each hook entry
in our pre-commit configuration.

…bels_workflow

Allow the `sync-labels` workflow to be run manually

…ons-monitor

Add the `GitHubSecurityLab/actions-permissions/monitor` Action

Explicitly define permissions of `GITHUB_TOKEN` in our GitHub Actions workflows

Update `pre-commit` hook versions

…hooks

Add additional hooks from `pre-commit/pre-commit-hooks`

…oks_are_sorted

Sort hook ids in each `pre-commit` hook entry

…skeleton

Add a directive for hashicorp/setup-packer that was missed when it was
added to the `build` workflow. Add a directive for
cisagov/setup-env-github-action that is not strictly necessary since we
currently just pull from the `develop` branch, but is good to have in
case we were to change that in the future.

Add missing dependabot ignore directives

Lineage pull request for: skeleton

…-non-nullable

Specify all variables as non-`nullable`

This agrees with the advice for Terraform modules given here:
https://developer.hashicorp.com/terraform/language/expressions/version-constraints#terraform-core-and-provider-versions

Note that these changes should not be made to root modules.

…ictions

Loosen version restrictions

…eton