chore(deps): widen pre-commit and python-kacl version bounds

[astanziola]

Summary

• Drop lower bounds for pre-commit (<5.0.0) and python-kacl (<0.8.0) since they're dev-only tools
• Resolves Update pre-commit requirement from <4.0.0,>=3.8.0 to >=3.8.0,<5.0.0 #154 and Update python-kacl requirement from <0.7.0,>0.6.0 to >0.6.0,<0.8.0 #156
• 319 tests pass

[Copilot]

Pull request overview

This PR updates the development dependency version constraints in pyproject.toml to widen the allowed ranges for pre-commit and python-kacl, aiming to reduce friction for dev-only tooling updates.

Changes:

• Widen pre-commit constraint to allow <5.0.0 (removing the lower bound).
• Widen python-kacl constraint to allow <0.8.0 (removing the lower bound).

---

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

[Copilot]

pre-commit<5.0.0 drops the lower bound and makes this entry inconsistent with the rest of the dev dependency group (which pins both lower+upper bounds). Keeping an explicit minimum (e.g., >=3.8.0) avoids resolvers selecting very old pre-commit versions if constraints change and helps ensure the repo’s .pre-commit-config.yaml remains compatible.

Suggested change

	"pre-commit<5.0.0",
	"pre-commit>=3.8.0,<5.0.0",

[Copilot]

python-kacl<0.8.0 also drops the lower bound. This tool is used by repo automation/docs via kacl-cli (e.g. the draft release workflow calls kacl-cli release ... --auto-link), so allowing very old versions can break contributor workflows/CI if a resolver ever picks an older release. Consider keeping an explicit minimum version known to support the CLI/options you use (previously >0.6.0).

Suggested change

	"python-kacl<0.8.0",
	"python-kacl>=0.6.0,<0.8.0",