Fix RefResolver store parameter type in jsonschema stubs

[sedat4ras]

Fixes #8662

Changes

In stubs/jsonschema/jsonschema/validators.pyi, the store parameter of RefResolver.__init__ was typed as SupportsKeysAndGetItem[str, str] | Iterable[tuple[str, str]], but the actual runtime implementation accepts a mapping/iterable of Mapping[str, Any] (i.e., full JSON schema objects), not plain str values.

The jsonschema source code uses URIDict (which inherits from MutableMapping[str, Any]) for the store, and the store values are schema documents (JSON objects), not strings.

Before:

store: SupportsKeysAndGetItem[str, str] | Iterable[tuple[str, str]] = ...,

After:

store: SupportsKeysAndGetItem[str, Mapping[str, Any]] | Iterable[tuple[str, Mapping[str, Any]]] = ...,

This matches the actual usage pattern where users pass schema documents as store values:

RefResolver("http://example.com/", schema, store={"http://example.com/other": other_schema})

[srittau]

Thanks, one request below.

Also, I noticed that URIDict in _utils.pyi also derives from MutableMapping[str, str]. This should probably also be changed to MutableMapping[str, MutableMapping[str, Any]] (and of course some method types need to be changed as well.) You could include these changes in this PR if you want to, but that's optional.

[srittau]

I just noticed something else: values() is called on store if it's a Mapping:

https://github.com/python-jsonschema/jsonschema/blob/a7277432b0f7bcd0551f6e589d30457017125df4/jsonschema/validators.py#L948-L952

While we usually try to avoid Mapping in new annotations, considerung that RefResolver is deprecated and will be removed at some point, just using it here is probably the most pragmatic solution.

[sedat4ras]

While I was switching store to Mapping, I kept looking at handlers and couldn't quite convince myself whether it needed the same treatment. As far as I can tell from the runtime source, it only does key lookups — no .values() or .items() calls — so I left it as SupportsKeysAndGetItem. But I'm not fully confident I didn't miss something, so just wanted to check: does that sound right to you?

[srittau]

Suggested change

	m: SupportsKeysAndGetItem[str, MutableMapping[str, Any]] | Iterable[tuple[str, MutableMapping[str, Any]]],
	m: Mapping[str, MutableMapping[str, Any]] | Iterable[tuple[str, MutableMapping[str, Any]]],

[sedat4ras]

Applied your suggestion — changed m parameter from SupportsKeysAndGetItem to Mapping and removed the now-unused import. Thanks for the review!

[github-actions]

According to mypy_primer, this change has no effect on the checked open source code. 🤖🎉