Fix CI matrix builds when automattic/vipwpcs supports v4 of squizlabs/php_codesniffer

[kasparsd]

Is your enhancement related to a problem? Please describe.

To run PHP compatibility checks with phpcompatibility/php-compatibility with the latest versions of PHP 8.x, we're requiring it as 10.x-dev as 9.99.99 which allows phpcompatibility/phpcompatibility-wp to still work (since it is locked at v9).

However, the 10.x-dev branch of phpcompatibility/php-compatibility was recently updated to require v4 of squizlabs/php_codesniffer which now conflicting with v3 required by automattic/vipwpcs.

During CI matrix runs we're removing the composer.lock file which makes it attempt a fresh resolution of dependencies.

Proposed Solution

Wait until VIP fixes Automattic/VIP-Coding-Standards#878 and update composer.json to use the latest version that supports v4 of squizlabs/php_codesniffer.

Designs

No response

Describe alternatives you've considered

The alternative is to remove automattic/vipwpcs until it is updated to fix the CI builds in the mean time.

Please confirm that you have searched existing issues in this repository.

Yes

[rodrigoprimo]

@kasparsd, have you considered using phpcompatibility/phpcompatibility-wp:3.3.0-alpha1 (https://github.com/PHPCompatibility/PHPCompatibilityWP/releases/tag/3.0.0-alpha1)? I believe this will solve the problem that you are having, and it is the recommended version. I don't know the details of this specific project, but I believe there is no need to require phpcompatibility/phpcompatibility directly in the composer.json file. Just requiring phpcompatibility/phpcompatibility-wp is usually enough.