chore(deps): update dependency phpstan/phpstan to ^2.1.51

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
phpstan/phpstan	^2.1.46 → ^2.1.47

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, 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 artifacts 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: composer.lock

Command failed: composer update phpstan/phpstan:2.1.47 --with-dependencies --ignore-platform-req=ext-* --ignore-platform-req=lib-* --no-ansi --no-interaction --no-scripts --no-autoloader --no-plugins --minimal-changes
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires phpstan/phpstan ^2.1.47, found phpstan/phpstan[2.1.47, 2.1.48, 2.1.49, 2.1.50] but these were not loaded, likely because it conflicts with another require.
  Problem 2
    - phpstan/phpstan-deprecation-rules is locked to version 2.0.4 and an update of this package was not requested.
    - phpstan/phpstan-deprecation-rules 2.0.4 requires phpstan/phpstan ^2.1.39 -> found phpstan/phpstan[2.1.39, ..., 2.1.50] but these were not loaded, likely because it conflicts with another require.
  Problem 3
    - phpstan/phpstan-phpunit is locked to version 2.0.16 and an update of this package was not requested.
    - phpstan/phpstan-phpunit 2.0.16 requires phpstan/phpstan ^2.1.32 -> found phpstan/phpstan[2.1.32, ..., 2.1.50] but these were not loaded, likely because it conflicts with another require.
  Problem 4
    - phpstan/phpstan-strict-rules is locked to version 2.0.10 and an update of this package was not requested.
    - phpstan/phpstan-strict-rules 2.0.10 requires phpstan/phpstan ^2.1.39 -> found phpstan/phpstan[2.1.39, ..., 2.1.50] but these were not loaded, likely because it conflicts with another require.
  Problem 5
    - rector/rector is locked to version 2.4.2 and an update of this package was not requested.
    - rector/rector 2.4.2 requires phpstan/phpstan ^2.1.48 -> found phpstan/phpstan[2.1.48, 2.1.49, 2.1.50] but it conflicts with your temporary update constraint (phpstan/phpstan:2.1.47).

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

File name: composer.json

Artifact update for phpstan/phpstan resolved to version 2.1.50, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 2.1.47
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/