Use Markdoc on the website

[emmatown]

This PR replaces MDX with Markdoc for the docs portion of the website. It does not actually remove MDX from the website because I skipped converting the updates/releases sections to use Markdoc since they do weirder things and they'll likely be going away soon, it didn't seem worthwhile converting them.

The reasoning behind this is so that we can easily statically analyze our docs (It's impractical to do that on MDX since it's literally code that could do anything) to get all the headings for a table of contents and etc. while preserving the ability to express more custom things that can't be represented with just Markdown

[changeset-bot]

⚠️ No Changeset found

Latest commit: c5c6aa1

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

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
keystone-next-docs	✅ Ready (Inspect)	Visit Preview	Aug 16, 2022 at 5:36AM (UTC)

[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.

Latest deployment of this branch, based on commit c5c6aa1:

Sandbox	Source
@keystone-6/sandbox	Configuration