Update dependency pre-commit to ~=4.2.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
pre-commit	~=3.5.0 -> ~=4.2.0

---

Configuration

📅 Schedule: Branch creation - "after 8am on saturday" in timezone Australia/Brisbane, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: uv.lock

Command failed: uv lock --upgrade-package pre-commit
Using CPython 3.13.3 interpreter at: /opt/containerbase/tools/python/3.13.3/bin/python3
  × No solution found when resolving dependencies for split
  │ (python_full_version == '3.8.*'):
  ╰─▶ Because only pre-commit{python_full_version < '3.9'}<=4.2.0 is available
      and the requested Python version (>=3.8, <4.0) does not satisfy
      Python>=3.9, we can conclude that pre-commit{python_full_version <
      '3.9'}>=4.2.0 cannot be used.
      And because apitally:dev depends on pre-commit{python_full_version <
      '3.9'}>=4.2.0 and your project requires apitally:dev, we can conclude
      that your project's requirements are unsatisfiable.

      hint: `pre-commit` was requested with a pre-release marker (e.g.,
      pre-commit>4.2.0,<4.3.dev0), but pre-releases weren't enabled (try:
      `--prerelease=allow`)