updates:
- [github.com/sirosen/check-jsonschema: 0.11.0 → 0.13.0](0.11.0...0.13.0)

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

This is a new org created to hold check-jsonschema and the jsonschema
package. As the repo has moved, various docs &c need minor tweaks to
avoid extra redirects through the old name.

Co-authored-by: sirosen <sirosen@users.noreply.github.com>

Rather than dedicated testing for `metaschemas/...`, the metaschema
hook can now be tested under the hook example files.

The configuration is basically the same as any other hook. As there
are schema-authors interested in writing YAML schemas, the YAML format
is supported for this purpose.

Add some YAML schema files for metaschema tests

* [vendor-schemas] automated update

* Update CHANGELOG.md

- move unit tests to `unit/`
- move the configured hooks test to the acceptance test dir

Parametrize tests over several sets of mutex options. Check that the
correct error is raised. Fix the absence of a required positional
which stopped the test from reaching the correct error.

- use a parametrized fixture rather than the same param list for each
  test
- check error messages against stderr
- check format checker behavior on non-str data

Make sure positive and negative test cases pass for 'file://' schemas.
Add a negative test case for a non-file, non-http(s) scheme, 'ftp://'
is used in the test as a "plausible" example.

In order for the test to pass, explicit handling needs to be
introduced for the UnsupportedUrlScheme error case, and the schema
reader object needs to be initialized lazily.

Given a local file URI on Windows, e.g. `file:///C:/foo.txt`, the path
was not properly being deduced as a Windows-native absolute path.
Instead, the path would be converted to a URI path with posix-like
notation, like `/C:/foo.txt`. The result didn't work for local
relative ref resolution because the resulting pathlib.Path object
isn't absolute (wrong slashes).

The fix is more manual and explicit handling of the file-URI case when
converting into a pathlib.Path object in the first place. Using
`urllib.requests.url2pathname`, imitate the solution from `pip` for
this same problem, simplifying a bit for the relevant case.

`filterwarnings=error`, which flags the following things to fix:
- match_querystring=False vs match_querystring=None for
  responses==0.17.0 (last version with py3.6 support)
- importlib_resources.files() vs "legacy" functions

To handle importlib_resources, it's important to tweak the
importlib_resources requirement to 'python_version<"3.9"'. This
guarantees that we always use a version which supports the newer
`files()` API.

Ensure we open files as binary. The alternative would be to use
`encoding="utf-8"` explicitly. Either is fine -- the point is to be
consistent.

* [vendor-schemas] automated update

* Update CHANGELOG.md

* [vendor-schemas] automated update

* Update CHANGELOG.md

Compat code for py36 to workaround versions of `identify` and
`jsonschema` can be removed if we move to py3.7+ only.

Update the build matrices, and the python_requires package metadata.

Set new lower bounds for `jsonschema` and `identify` to match the
needed newer features.

Import future annotations and use pyupgrade to update the style of
annotations in use throughout the codebase. Add some annotations where
appropriate.

- setup mypy
- enable mypy in CI and add it to `make lint`
- do requisite cleanup to make mypy pass
- add a changelog note for removal of py36 and addition of
  mypy usage