chore(components): sub in storybook for styleguidist

[b-cooper]

Overview

This migrates the sandbox renderer for our component library from styleguidist to storybook.

In addition to working cleanly with TypeScript, Storybook has more features and flexibility compared with styleguidist.

Give it a whirl here

TODOs

• create stories for all non-deprecated components
• hook up storybook to build and deploy machinery
• remove vestiges of styleguidist

Following Work

• react-storybook's usage of react-docgen is not fully operational in this PR, a follow up should address this and take advantage of richer docstring parsing making it into the Docs tab of each component's story.
• stories are currently being excluded from tsconfig as well as eslint to sidestep an issue with storybook's usage of emotion conflicting with our usage of styled-components. This should be mended soon, so that our stories can take advantage of linting and typechecking.

Changelog

• make Component.stories.tsx for each non-deprecated component story in the library
• hoist storybook functionality to the root of the repo to allow us to put stories anywhere across JS files in our mono-repo
• remove all styleguidist markdown files
• add TODO comments to components that didn't require stories, tag them for later reorganization

Review requests

• [] try run make dev -C components locally and confirm that it starts the storybook dev server.

Risk assessment

low, no code should have been altered

[mcous]

First review pass, 77 out of 114 files. I think the lack of linting and autoformatting on the stories is making this review a little harder, so opened #7708 to get that working

[mcous]

Took a pass at this, and looks good to me!

• Can build storybook locally
• Can run dev server locally
• CI builds look like they're working
• No source code changes to actual components

Lack of typechecking in components in annoying, but for now, VS Code still handles the files in isolation, so that's not the worst

[shlokamin]

Not sure what's going on but it seems like storybook isn't getting installed after a make setup-js. there is something weird happening after i do a make teardown-js, but i dont think that's the issue. Any idea what this could be?

[shlokamin]

out of curiosity how come we gotta bump this up?

[mcous]

Not bumping it can result in flow crashing with Unhandled exception: SharedMem.Hash_table_full 🙃

But yeah, as the codebase grew, we started seeing that particular flow crash. Added the config to bump it up to 20 in #4959. As Brian was working on this PR, he started seeing this crash again, and bumping it again (from 16 MB to 32 MB) seemed to resolve it.

Since Flow is on its way out, it seemed like the most straightforward thing to do to keep things chugging along rather than investigating it too deeply

[shlokamin]

how come we're switching this to port 6060? upon googling looks like 6060 is used to indicate the use of the X Windows Protocol which i'd never heard of!

[mcous]

😬 so yeah, turns out we never used this $(port) variable. If you run make -C components dev in edge right now, the dev server will launch on port 6060. This PR changes this value to match the currently used port and actually uses it in the make dev target now