Signed-off-by: Filipe Laíns <lains@riseup.net>

3.6 reached its EOL in Dec of last year and our main dependencies
(pep517 and packaging) have already dropped support for it.

updates:
- [github.com/asottile/pyupgrade: v3.1.0 → v3.2.2](asottile/pyupgrade@v3.1.0...v3.2.2)
- [github.com/pre-commit/mirrors-prettier: v3.0.0-alpha.2 → v3.0.0-alpha.4](pre-commit/mirrors-prettier@v3.0.0-alpha.2...v3.0.0-alpha.4)

Signed-off-by: Henry Schreiner <henryschreineriii@gmail.com>

This patch is intended to lower the maintenance burden of having to
manually go through each matrix subjob name in the branch protection
repository settings. It allows to only include the `check` job in the
branch protection and it will robustly determine if the dependencies
have succeeded or not.

It is currently mostly serves the Python ecosystem in projects like
aiohttp, attrs, cryptography, pydantic, open edX, pip etc. But I've
also seen other communities picking it up lately, like the AWS Rust
SDK and even the engine powering https://dev.to, to my surprise.
Strictly speaking, it is agnostic.

Ref: https://github.com/marketplace/actions/alls-green#why

updates:
- [github.com/pre-commit/pre-commit-hooks: v4.3.0 → v4.4.0](pre-commit/pre-commit-hooks@v4.3.0...v4.4.0)
- [github.com/PyCQA/flake8: 5.0.4 → 6.0.0](PyCQA/flake8@5.0.4...6.0.0)

updates:
- [github.com/asottile/pyupgrade: v3.2.2 → v3.3.0](asottile/pyupgrade@v3.2.2...v3.3.0)

Signed-off-by: Henry Schreiner <henryschreineriii@gmail.com>

Signed-off-by: Henry Schreiner <henryschreineriii@gmail.com>

updates:
- [github.com/asottile/pyupgrade: v3.3.0 → v3.3.1](asottile/pyupgrade@v3.3.0...v3.3.1)
- [github.com/psf/black: 22.10.0 → 22.12.0](psf/black@22.10.0...22.12.0)
- [github.com/PyCQA/isort: 5.10.1 → 5.11.4](PyCQA/isort@5.10.1...5.11.4)

Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>

Signed-off-by: Filipe Laíns <lains@riseup.net>