Move changeset for #6907 into .changeset folder

[JedWatson]

Not sure how this happened, but I realised that the changeset for #6907 was in the repo root, not the .changeset folder which would have caused issues with the next release + changelog

[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/nMyt3MjaFb4mfboUGSQ6VrMREeCW
✅ Preview: https://keystone-next-docs-git-fix-6907-changeset-keystonejs.vercel.app

[changeset-bot]

⚠️ No Changeset found

Latest commit: 71fdaa5

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 changesets to release 15 packages

Name	Type
@keystone-next/keystone	Minor
@keystone-next/auth	Major
@keystone-next/cloudinary	Major
@keystone-next/fields-document	Major
@keystone-next/session-store-redis	Major
@keystone-next/example-auth	Patch
@keystone-next/examples-app-basic	Patch
@keystone-next/example-ecommerce	Patch
keystone-next-app	Patch
@keystone-next/example-roles	Patch
@keystone-next/example-sandbox	Patch
@keystone-next/example-testing	Patch
@keystone-next/example-with-auth	Patch
@keystone-next/website	Patch
@keystone-next/example-document-field	Patch

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

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.