Fix Jest devDependency version alignment (remove jsdom, pin jest-util to v29)

[Copilot]

Description

package.json had a version skew where jest was pinned to v29 but jest-environment-jsdom and jest-util were both pulling v30 — causing resolver conflicts and a mixed lockfile.

Changes:

• Removed jest-environment-jsdom — jest.config.js sets testEnvironment: 'node'; jsdom was never used
• Downgraded jest-util from ^30.3.0 → ^29.7.0 — it's a declared peer dep of ts-jest and must align with jest's major version

All Jest-related devDeps (jest, jest-util, @types/jest, ts-jest) now consistently target v29.

Type of Change

• 🐛 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 📝 Documentation update
• 🎨 Code style update (formatting, renaming)
• ♻️ Refactoring (no functional changes)
• ⚡ Performance improvement
• ✅ Test update

Related Issue

Closes #

Testing Done

• Tested locally
• Added/updated tests
• All tests passing

Screenshots (if applicable)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• Any dependent changes have been merged and published

Co-Authors

---

💬 Send tasks to Copilot coding agent from Slack and Teams to turn conversations into code. Copilot posts an update in your thread when it's finished.

---

Summary by cubic

Aligns Jest devDependencies to v29 to fix version mismatches in the test setup. Removes jest-environment-jsdom (not used; tests run in Node) and pins jest-util to ^29.7.0.

^{Written for commit 97e3d07. Summary will update on new commits.}