Access control API docs

[timleslie]

Preview deployment here: https://keystone-next-docs-git-access-control-api-keystonejs.vercel.app/apis/access-control

[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/8kb1ojWRQmoUqspnUFkZNyCca95g
✅ Preview: https://keystone-next-docs-git-access-control-api-keystonejs.vercel.app

[changeset-bot]

⚠️ No Changeset found

Latest commit: 7c30119

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

[gautamsi]

@timleslie I wanted to remind you of condition in #3239 which was fixed in #3241, there was one condition left that it may still have incorrect sequence if user has no access to update some items (based on declarative control like isLocked = true) then the sequence in the resolveInput and afterChange would be different in the array.

I can explain more if it does not remind you full context.

[timleslie]

@timleslie I wanted to remind you of condition in #3239 which was fixed in #3241, there was one condition left that it may still have incorrect sequence if user has no access to update some items (based on declarative control like isLocked = true) then the sequence in the resolveInput and afterChange would be different in the array.

I can explain more if it does not remind you full context.

Thanks for the reminder of these. I'm going to follow this up with a separate PR to fix that behaviour.

[JedWatson]

Nice!