build: update Composer & NPM deps

[justlevine]

What

Updates the deps to their latest version

Why

Prelease work

Related Issue(s):

How

AI Disclosure

Testing Instructions

Screenshots

Additional Info

Checklist

• I have read the Contribution Guidelines.
• My PR title is descriptive and follows the conventional commit message format.
• My code passes all lints (PHPCS, PHPStan, ESLint, etc.).
• My code has detailed inline documentation.
• My code has tests that cover the changes I made.
• I have updated the project documentation as needed.

[Copilot]

Pull request overview

Updates the repository’s JS (npm) and PHP (Composer) dependency locks to newer versions, primarily to keep the WordPress block-editor/tooling stack and PHPStan current.

Changes:

• Bump @wordpress/* runtime deps (e.g., block-editor, blocks, i18n, interactivity) and related dev tooling (@wordpress/scripts, @wordpress/env, lint configs).
• Update TypeScript ESLint tooling versions and add corresponding npm overrides.
• Update Composer lock (notably phpstan/phpstan) and regenerate lock metadata with a newer Composer.

Reviewed changes

Copilot reviewed 1 out of 3 changed files in this pull request and generated no comments.

File	Description
package.json	Updates direct JS deps/devDeps and adds npm overrides for updated tooling.
package-lock.json	Regenerates npm lockfile for the updated dependency graph.
composer.lock	Updates locked PHP tooling (e.g., PHPStan) and Composer lock metadata.

---

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