Identify sniffs related to VIP Go platform compatibility

## What problem would the enhancement address for VIP?

It would be useful if there was a way for clients to see a more granular report for checking VIP Go platform compatibility in regards to functionality requirements.

## Describe the solution you'd like

Currently, we have a "Compatibility" folder, but there's only one sniff in it (that is to be deprecated). However, a lot of the sniffs live in the other categories since when they were first categorized, compatibility was seen as a secondary category. There are a few ways to go about it that I can see:

Option A) Maintain a separate ruleset aka WordPress-VIP-Compatibility (after #600 has completed).

Option B) For #600, move those sniffs into the Compatibility folder since we are breaking error codes anyways.

(interim) Option C) Have a paste-able command available for clients who want to run that type of check in our docs e.g.

```
phpcs --standard=WordPress-VIP-Go --sniffs=
```

Beginne mit der Durchsicht des Ordners Compatibility und seines vorhandenen Sniffs. Lies anschließend den Kontext von Issue #600 und die anderen Sniff-Kategorien. Abgeschlossen ist die Aufgabe, wenn eine konkrete Möglichkeit zur Identifizierung von VIP Go-Kompatibilitäts-Sniffs ausgewählt und dokumentiert wurde, etwa ein separates Regelwerk, eine Neuklassifizierung oder ein dokumentierter phpcs-Befehl.

Vom Indexierungsmodell aus dem Issue-Text verfasst.