Chore/wp graphql cs

[theodesp]

Description

Merge of #126 with some ignores. Commit history is maintained.

Testing

1. Setup docker-compose
2. Run unit tests
3. Run lint tests

They should all pass

[changeset-bot]

⚠️ No Changeset found

Latest commit: 820e841

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[justlevine]

@theodesp I branched this and updated to the latest wp-graphql-cs in #163, which includes the latest 3.0.x versions of WPCS/VIPCS, for your review 🙏

[mindctrl]

The schema linter detected breaking changes, but it appears to be unrelated to this PR (and maybe related to WPGraphQL changes?):

Detected the following changes (73) between schemas:
[log] ✖  Field EnqueuedAsset.dependencies changed type from [EnqueuedScript] to [EnqueuedAsset]
[log] ✖  Field EnqueuedStylesheet.dependencies changed type from [EnqueuedScript] to [EnqueuedStylesheet]

Otherwise looks good to me.

[justlevine]

The schema linter detected breaking changes, but it appears to be unrelated to this PR (and maybe related to WPGraphQL changes?):

Detected the following changes (73) between schemas:
[log] ✖  Field EnqueuedAsset.dependencies changed type from [EnqueuedScript] to [EnqueuedAsset]
[log] ✖  Field EnqueuedStylesheet.dependencies changed type from [EnqueuedScript] to [EnqueuedStylesheet]

Otherwise looks good to me.

@mindctrl 🎯. Leaking from wp-graphql/wp-graphql#2988