feat: bump deps on data packages, and update tests which reach within the transformer interface

[alharris-at]

Description of changes

• Bump to next major version of amplify transformer dependencies.
• Update mock utility tests to shim a synth in order to test the underlying transformers (this is a dupe of changes made in API category).
• Remove graphql-migration-tests since the v1->v2 transformer behavior should be fully tested within the API category, and re-testing here is not a frugal use of resources. The reason we left e2e tests in both repos was to ensure that interactions across categories would be tested, but these tests validate strictly the behavior of the transformer.
• Remove unused dep on transformer core from cloudformation provider package.

This PR pulls in the following releases:

• Amplify API Category 5.5.3
• Amplify API Category 5.6.0
• Amplify API Category 5.6.1
• Amplify Codegen Utility 4.4.0

Which consists of the following changes:

• chore: 🤖 add support for ap-northeast-3 KIX by @petercwk-aws in chore: 🤖 add support for ap-northeast-3 KIX amplify-category-api#1741
• ci: remove cci assets by @AaronZyLee in ci: remove cci assets amplify-category-api#1731
• chore: improve DX for SSHing to debug failed E2E by @phani-srikar in chore: improve DX for SSHing to debug failed E2E amplify-category-api#1744
• chore: dx improvement for codebuild by @AaronZyLee in chore: dx improvement for codebuild amplify-category-api#1752
• chore: use cli RC to remove dev dep on vm2 by @dpilch in chore: use cli RC to remove dev dep on vm2 amplify-category-api#1774
• Merge Refactor of GraphQL Transformer Concerns into Main Branch by @alharris-at in Merge Refactor of GraphQL Transformer Concerns into Main Branch amplify-category-api#1751
• chore: use plain ts for cred rotate by @AaronZyLee in chore: use plain ts for cred rotate amplify-category-api#1772
• feat: store construct output by @dpilch in feat: store construct output amplify-category-api#1721
• chore: add api extractor to missing packages by @alharris-at in chore: add api extractor to missing packages amplify-category-api#1789
• fix: allow update on operations create, read, update by @dpilch in fix: allow update on operations create, read, update amplify-category-api#1762
• feat: bump major version of transformer packages by @alharris-at in feat: bump major version of transformer packages amplify-category-api#1790
• chore: use tagged cli release which relies on new MV bump by @alharris-at in chore: use tagged cli release which relies on new MV bump amplify-category-api#1793
• style: fix eslint rule import/export by @dpilch in style: fix eslint rule import/export amplify-category-api#1713
• fix: compile error in canary by @AaronZyLee in fix: compile error in canary amplify-category-api#1799
• feat: store api id on stack output by @sdstolworthy in feat: store api id on stack output amplify-category-api#1801
• feat: add model schema uri to outputs by @alharris-at in feat: add model schema uri to outputs amplify-category-api#1810
• fix: don't perform sub if bucketName is an unresolved token by @alharris-at in fix: don't perform sub if bucketName is an unresolved token amplify-category-api#1814
• chore: add additional cdk e2e tests for relationships by @alharris-at in chore: add additional cdk e2e tests for relationships amplify-category-api#1820
• chore: add back in backwards compatibility apis to core transformer by @alharris-at in chore: add back in backwards compatibility apis to core transformer amplify-category-api#1818
• chore: fix api lambda migration test by @alharris-at in chore: fix api lambda migration test amplify-category-api#1821
• fix: reading admin role names by @phani-srikar in fix: reading admin role names amplify-category-api#1823
• fix(graphql-schema-validation): relationship names not unique by @bzsurbhi in fix(graphql-schema-validation): relationship names not unique amplify-category-api#1819
• fix: cannot read properties of undefined by @AaronZyLee in fix: cannot read properties of undefined amplify-category-api#1804
• feat: add type branding to graphql in TS outputs by @svidgen in feat: add type branding to graphql in TS outputs amplify-codegen#623

Issue #, if available

N/A

Description of how you validated changes

Unit + E2E tests https://app.circleci.com/pipelines/github/aws-amplify/amplify-cli/22801/workflows/ec9ea148-08d9-4982-a6bb-0896540402aa

Checklist

• PR description included
• yarn test passes
• Tests are changed or added

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[awsluja]

lgtm

[sobolk]

Why?

[alharris-at]

Type is no longer exported from our core packages, and this type isn't actually used anywhere in the system. I could import the type directly, but instead elected to just leave this as an any which was the state before we added these facades.