Switch PHPCS from the squizlabs to phpcsstandards package

[tomjn]

The squizlabs package comes from a repo with no active admins, and active maintenance moved to the PHPCS Standards org, this repo should use the new package, especially given there are already phpcsstandards packages in use here

[mlipe-nxs]

I think it would be great to start using the new package, however both the wp-coding-standards and automattic packages are still using the squizlabs version as the runner and within the ruleset configurations.

I'm reluctant to have 2 versions of the basically the same package even though technically they have different namespaces.

Also, there are a lot of unit tests which fail after making this change which would need to be reconciled.

[lipemat]

Testing the new composer.json I also discovered the bin (phpcs and phpcbf) scripts still point to the squizlabs version which basically negates the value of making this change.

[tomjn]

What can we do to help assist the process in dependencies?

https://twitter.com/jrf_nl/status/1730583893537898786

• VIPCS: Switch to PHPCSStandards/PHP_CodeSniffer & raise minimum supported version Automattic/VIP-Coding-Standards#805
• WPCS: Switch to PHPCSStandards/PHP_CodeSniffer & raise minimum supported version WordPress/WordPress-Coding-Standards#2408

[jrfnl]

Thank you for your support and your enthousiasm embracing the take-over of the PHP_CodeSniffer package.

In contrast to earlier information, arrangements are now being made to allow the package to continue under its original name on Packagist. The commit (in the new repo) to rename the package has been reverted.

I'd recommend reverting the Composer reference changes and keeping the changes which refer to the repo URL on GitHub.

Sorry for the confusion and thank you for understanding. I hope you'll enjoy the 3.8.0 release, which I expect to release this Friday.