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=
```

首先检查 Compatibility 文件夹及其中现有的 sniff，然后阅读 issue #600 的上下文和其他 sniff 类别。完成的标准是选择并记录一种识别 VIP Go 兼容性 sniff 的具体方式，例如单独的 ruleset、重新分类或记录一个 phpcs 命令。

由索引模型根据 Issue 内容生成。