Update .sudo() to use the internal schema

[timleslie]

The static access control rule access: false will remove the related queries/mutations from the graphQL schema. When using the .sudo() context we want to be able to run commands while ignoring access control. This implies that we should be able to execute the queries/mutations associated with the item marked access: false.

To make this work we can take advantage of the internal schema which is provided by Keystone core, which is a full version of the schema without any of the operations removed.

The net impact of this change is to have .sudo() behave the way a user would expect, in that they can perform all possible operations in the system.

This change is required in order for us to test the access control package, as we need to be able to execute mutations on lists with { access: false }.

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/keystonejs/keystone-next-docs/CL4zFiLUhjiD58L21EWDkzSHsEpY
✅ Preview: https://keystone-next-docs-git-internal-sudo-keystonejs.vercel.app

[changeset-bot]

🦋 Changeset detected

Latest commit: 5414063

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 10 packages

Name	Type
@keystone-next/keystone	Minor
@keystone-next/types	Minor
@keystone-next/test-utils-legacy	Patch
@keystone-next/auth	Major
@keystone-next/example-auth	Patch
@keystone-next/app-basic	Patch
@keystone-next/example-ecommerce	Patch
keystone-next-app	Patch
@keystone-next/example-roles	Patch
@keystone-next/example-todo	Patch

Not sure what this means? Click here to learn what changesets are.

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