build(deps): bump pymdown-extensions from 10.21.3 to 11.0.1 in the uv group across 1 directory

[dependabot]

Bumps the uv group with 1 update in the / directory: pymdown-extensions.

Updates pymdown-extensions from 10.21.3 to 11.0.1

Release notes

Sourced from pymdown-extensions's releases.

11.0.1

• FIX: BetterEm: Fix regex pattern inefficiencies.
• FIX: Tilde: Fix regex pattern inefficiencies.
• FIX: Caret: Fix regex pattern inefficiencies.
• FIX: MagicLink: Fix regex pattern inefficiencies.

11.0

• BREAK: B64: Restricts relative links to base_path by default. Can be disabled by setting new restrict_path option to False. The new root_path can be specified if paths are desired to be restricted to a different location separate base_path which is also used as a relative base for image paths.
• NEW: Drop Python 3.9 support.
• FIX: Tabbed: Fix issue where an empty title would cause an exception.

Commits

• c684985 Merge commit from fork
• 6d0097b Update changelog
• f4808ea Bump version and update changelog
• a290074 Update JS doc deps
• edce355 Merge commit from fork
• 9fb9643 Update Python type deps
• 299a129 Docs: Update JS deps
• 367d965 Drop Python 3.9 (#2902)
• 19ec936 Fix issue with empty titles and Tabbed (#2901)
• 4868783 Fix npm option
• Additional commits viewable in compare view

[robcohen]

Verified before merging, because nothing in CI builds the docs — pymdown-extensions is a transitive dependency of the docs group (via mkdocs-material and mkdocstrings), and no workflow runs mkdocs. So the 27 passing checks say nothing about this bump, which matters more than usual for a 10 → 11 major.

mkdocs.yml uses three of its extensions directly (pymdownx.highlight, pymdownx.superfences, pymdownx.inlinehilite), so I built the site on both versions and compared:

	10.21.3	11.0.1
mkdocs exit	1	1
warnings	4	4
warning text	identical	identical
generated HTML	—	byte-identical, all 8 pages

So the major bump is a genuine no-op for this site.

Separately, and not caused by this PR: mkdocs build --strict already fails on main with 4 warnings — three dead links (../contrib/docker/README.md twice, ../SECURITY.md) and one griffe docstring parse warning in query_shell.py:229. Since docs aren't built in CI, that has no way of being noticed. Worth either wiring a docs build into CI or fixing the links; happy to do either, but it's a separate change from a dependency bump.