String date format check allows unexpected formats with Python 3.11 and later
Looks like `date` format check uses `datetime.date.fromisoformat()`. The behavior changed in Python 3.11, allowing e.g. `2023-W01` and `20230315` style strings.

Running this with Python 3.11.x and having `jsonschema[format]` installed:
```python
#!/usr/bin/env python
"""
Show jsonschema `date` string format check behavior.

Looks like jsonschema uses `datetime.date.fromisoformat()` for the validation.
Python 3.11 changed `.fromisoformat()` behavior so that it accepts more
variants than just `YYYY-MM-DD`.

https://docs.python.org/3/library/datetime.html#datetime.date.fromisoformat
> Changed in version 3.11: Previously, this method only supported the format YYYY-MM-DD.

https://json-schema.org/understanding-json-schema/reference/string.html#dates-and-times

https://www.rfc-editor.org/rfc/rfc3339#section-5.6

"""
import sys

import jsonschema

schema = {
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "type": "string",
    "format": "date",
}

values = [
    ("2023-03-15", True),
    ("2023-02-29", False),
    ("2023-W01", False),
    ("2023-001", False),
    ("20230315", False),
    ("1969-12-31", True),
    ("2038-01-20", True),
]

print("Python", sys.version.split()[0])

cls = jsonschema.validators.validator_for(schema)
cls.check_schema(schema)
validator = cls(schema, format_checker=cls.FORMAT_CHECKER)
print(validator)

for value, expected in values:
    is_valid = validator.is_valid(value)
    print(f" {value=} {is_valid=} {expected=}")

```

results in this:
```
3.11.1
Draft202012Validator(schema={'$schema': 'https://json...020-12/schema', 'format': 'date', 'type': 'string'}, format_checker=<FormatChecker checkers=['date', 'date-time', 'duration', 'email', 'hostname', 'idn-email', 'idn-hostname', 'ipv4', 'ipv6', 'iri', 'iri-reference', 'json-pointer', 'regex', 'relative-json-pointer', 'time', 'uri', 'uri-reference', 'uri-template', 'uuid']>)
value='2023-03-15' is_valid=True expected=True
value='2023-02-29' is_valid=False expected=False
value='2023-W01' is_valid=True expected=False
value='2023-001' is_valid=False expected=False
value='20230315' is_valid=True expected=False
value='1969-12-31' is_valid=True expected=True
value='2038-01-20' is_valid=True expected=True
```

Quickly looking at the code it feels like a regular expression match `^\\d{4}-\\d{2}-\\d{2}$` _and_ keeping the `fromisoformat()` call would be the easiest fix.

See
* https://docs.python.org/3/library/datetime.html#datetime.date.fromisoformat
* https://github.com/python/cpython/commit/1303f8c927227b72d9ee9eae890be4692b4d4592
diff --git a/jsonschema/_format.py b/jsonschema/_format.py
index d274c5f..2231f5e 100644
--- a/jsonschema/_format.py
+++ b/jsonschema/_format.py
@@ -17,6 +17,8 @@ _RaisesType = typing.Union[
     typing.Type[Exception], typing.Tuple[typing.Type[Exception], ...],
 ]
 
+_RE_DATE = re.compile(r"^\\d{4}-\\d{2}-\\d{2}$", re.ASCII)
+
 
 class FormatChecker:
     """
@@ -396,7 +398,10 @@ def is_regex(instance: object) -> bool:
 def is_date(instance: object) -> bool:
     if not isinstance(instance, str):
         return True
-    return bool(instance.isascii() and datetime.date.fromisoformat(instance))
+    return bool(
+        _RE_DATE.fullmatch(instance)
+        and datetime.date.fromisoformat(instance)
+    )
 
 
 @_checks_drafts(draft3="time", raises=ValueError)
['jsonschema/_format.py']