ci: update pre-commit hooks to latest stable versions

[syedjafri06193]

• pre-commit-hooks: v4.6.0 -> v6.0.0
• pyproject-fmt: v2.5.0 -> v2.23.0

isort (9.0.0a3) and mdformat (1.0.0) were intentionally skipped —
pre-release and major version bumps respectively that may introduce
breaking changes.

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[adk-bot]

Response from ADK Triaging Agent

Hello @syedjafri06193, thank you for creating this PR!

To help us review and merge your pull request, please make sure to address the following items according to our contribution guidelines:

• Contributor License Agreement (CLA): It looks like the CLA check has failed. Please make sure to sign the Google CLA so we can accept your contribution.
• Testing Plan: Please include a testing plan section in your PR description detailing how you verified these pre-commit hook updates.
• Associated Issue: All PRs, other than small documentation or typo fixes, should have an associated issue. If a relevant issue doesn't exist, please create one and link it to this PR, or describe the feature directly within the PR description following the issue templates.

This information will help reviewers to review your PR more efficiently. Thanks!

[adk-bot]

I will read the SKILL.md for the adk-pr-analyze skill to understand the correct procedure for analyzing and triaging the GitHub Pull Request.I will first run the verification helper script to verify the contributor's Google CLA status and get the PR metadata, as required by the mandatory entry gate.I will use the custom fetch_github_pr tool to retrieve the pull request details and metadata.## 🚫 ADK Pull Request Analysis Refusal: PR #6028

Compliance Status: FAILED (Google CLA Not Signed)

Under the repository’s contribution policies and compliance gates, code analysis, triage, or any workspace operations on a pull request cannot be performed unless the contributor has signed the Google Contributor License Agreement (CLA).

Our verification of the pull request metadata for PR #6028 shows:

1. Google CLA Bot Check: The automated google-cla[bot] check has failed, and a notice has been left requesting that the author (@syedjafri06193) sign the agreement.
2. ADK Bot Notice: An automated notification from @adk-bot has confirmed that the CLA check is in a failed state.

Compliance Refusal

Caution

COMPLIANCE ACTION REQUIRED
Because the Google CLA has not been signed by the contributor, we absolutely refuse to run any further analysis, triage, diff-fetching, or checkout operations for PR #6028. All tooling operations have been halted immediately.

Once the contributor signs the Google CLA and the automated checks pass, please re-run the /adk-pr-analyze 6028 command to perform a full technical and architectural review.

---

Summary of work: Checked PR #6028 metadata using fetch_github_pr, verified that the Google CLA is unsigned, and halted further analysis in strict compliance with the adk-pr-analyze guidelines.