Update the WPCS-related composer dependencies

[anton-vlasenko]

What?

This PR updates the WPCS-related composer dependencies to ensure alignment between the Gutenberg and WordPress Core projects.

Why?

It is essential for both codebases to use the same versions of composer packages. This helps streamline the synchronization process and maintain consistency between the codebases.

How?

• Update Gutenberg to use the same WPCS and related packages as WordPress Core;
• Update GBCS to match the composer dependency versions used by WPCS;
• Fix the fatal error in AbstractSniffUnitTest caused by differing method signatures.

Testing Instructions

1. Review the changes and confirm that all CI jobs pass successfully.
2. Navigate to the test/php/gutenberg-coding-standards directory.
3. Run the PHPUnit tests with the following command:

   composer run-tests

4. Verify that all unit tests pass without errors.

[github-actions]

Flaky tests detected in b46a702.
Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.

🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/12590241734
📝 Reported issues:

• [Flaky Test] Navigates the items list via UP/DOWN arrow keys #64334 in /test/e2e/specs/site-editor/dataviews-list-layout-keyboard.spec.js
• [Flaky Test] submenu click on the arrow interactions #61884 in /test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: anton-vlasenko <[email protected]>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.