[SITE-1547] Add catalog-info.yml

…0923

Rename catalog-info.yml to catalog-info.yaml

* Add @pantheon-systems/devrel to coding standards codeowners

* Update CODEOWNERS

Co-authored-by: Phil Tyler <[email protected]>

---------

Co-authored-by: Phil Tyler <[email protected]>

this way we're informed of dependency updates

This is an issue that is likely coming from PHPCompatibility or PHPCompatibility-WP. The issue was present in WPCS (but fixed in 3.0). There is no real benefit for leaving error reporting in when it has to do with a CS ruleset, so I think we can safely just ignore errors.
See: WordPress/WordPress-Coding-Standards#2035
See also: https://gist.github.com/shreyasikhar/f4495ac952586096eb81d505e9e914a4

Updates the requirements on [fig-r/psr2r-sniffer](https://github.com/php-fig-rectified/psr2r-sniffer) to permit the latest version.
- [Release notes](https://github.com/php-fig-rectified/psr2r-sniffer/releases)
- [Commits](php-fig-rectified/psr2r-sniffer@1.5.0...2.2.1)

---
updated-dependencies:
- dependency-name: fig-r/psr2r-sniffer
  dependency-version: 2.2.1
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Updates the requirements on [yoast/phpunit-polyfills](https://github.com/Yoast/PHPUnit-Polyfills) to permit the latest version.
- [Release notes](https://github.com/Yoast/PHPUnit-Polyfills/releases)
- [Changelog](https://github.com/Yoast/PHPUnit-Polyfills/blob/4.x/CHANGELOG.md)
- [Commits](Yoast/PHPUnit-Polyfills@1.0.0...4.0.0)

---
updated-dependencies:
- dependency-name: yoast/phpunit-polyfills
  dependency-version: 4.0.0
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Add DisallowRenameFunctionSniff to enforce restrictions on rename() usage

* remove phpcs stuff

* exclude the wp rename sniff
wp warns, we error

* add a file to test the sniff against

* add a script to run tests

* add a composer test to test tests

* test tests on push

* exclude deprecated sniff from standards

* fix spacing

* add emoji

* properly ignore deprecated sniff

* add a comment for why we're excluding

* autoload both classes

* Group pantheon rules together

* exclude the multiline slash comment rule
we're redeclaring in Pantheon-WP with a higher severity

* duplicate exclusions in -Minimum
We need to redeclare because we're redeclaring the parent rulesets

* exclude deprecated VIP CSS/JS checks

* add our Pantheon-WP checks

* add DisallowMultilineSlashCommentSniff to enforce single-line comment usage

* feat(sniffs): add sniff to disallow multiline slash comments

Introduces the new `DisallowMultilineSlashCommentSniff` to improve comment consistency and readability.

This sniff performs two main checks:
- It flags consecutive single-line `//` comments, enforcing the use of `/* ... */` block syntax for multiline comments.
- It issues a warning for any comment line that exceeds 80 characters to encourage better formatting.

* add test cases for sniffs

* add helper scripts
so we can test things manually easier

* break the reusable single line comment code into a static method

* use the static method to call the single line comment sniff

* update the tess to support passing a ruleset to test

* add line breaks between tests for readability

* change echo to printf for portability

* use file headers to determine test name

* just echo an empty line

* maybe a space?

* add an error param
so the severity level can be adjusted

* pass an error for Pantheon-WP

* include severity in the tests

* add new test case

* don't flag inline comments