chore: add slugify config to toc extension

[bharvey88]

Summary

Adds the same slugify(case: lower) config to the toc: extension that PR #739 added to pymdownx.tabbed. The warning persisted after #739 because toc was still falling back to pymdown's default slugifier (the deprecated uslugify). Adding it explicitly to both extensions silences the warning.

Why

After #739 the build still emits 'uslugify' is deprecated because toc had no slugify configured and was using the legacy default.

Behavior change

None. case: lower matches the previous behavior; existing TOC anchor URLs are unchanged.

Test plan

• Build runs without the 'uslugify' is deprecated warning
• Existing page anchors / permalinks still resolve unchanged

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

🗂️ Base branches to auto review (1)

• beta

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: f2834692-a9f9-497a-b2cf-25c7415294c0

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch dev

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}