chore(ci): use strict docs building

[JP-Ellis]

📝 Summary

This prevents warnings from going unnoticed.

🚨 Breaking Changes

🔥 Motivation

There was a recent update which broke our docs, and this went unnoticed due to the warnings not resulting in failure.

🔨 Test Plan

CI

🔗 Related issues/PRs

[Copilot]

Pull request overview

This PR adds strict mode to the documentation build process to ensure that warnings are treated as errors, preventing documentation issues from going unnoticed in CI.

Key changes:

• Adds --strict flag to the mkdocs build command in the GitHub Actions workflow

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 51%. Comparing base (a7ac6a9) to head (250f205).
⚠️ Report is 1 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@         Coverage Diff          @@
##           main   #1382   +/-   ##
====================================
  Coverage    51%     51%           
====================================
  Files        31      31           
  Lines      3729    3729           
====================================
  Hits       1938    1938           
  Misses     1791    1791           

Flag	Coverage Δ
tests	51% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.