Move gatsby docs to Storybook

[langermank]

What are you trying to accomplish?

This is part 1 of moving all Gatsby content to Storybook to support the new docs IA. Part 2 includes upgrading Storybook to improve the markdown docs experience, and removing Gatsby completely.

I had to break this into two PRs because Gatsby doesn't like the Storybook 7 upgrade and I've wasted days trying to fix it. Once this PR is merged, I'll set up redirects to the Storybook markdown doc pages so we can safely delete Gatsby in the followup.

What approach did you choose and why?

• Copy code examples and markdown from Gatsby
• Bare minimum Storybook config. Docs are not working as expected but this will be solved with the upgrade to SB7
• Only write stories for components that do not exist in PVC

What should reviewers focus on?

• Check the Storybook deploy and make sure you can access the written docs content

Can these changes ship as is?

• Yes, this PR does not depend on additional changes. 🚢

[changeset-bot]

⚠️ No Changeset found

Latest commit: 1ada626

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