Add React Storybook for isolated debugging & roadmapping

[ramfox]

add stories for our chrome components:

• [ ] Button
• [ ] Dropdown
• [ ] DropdownMenu
• [ ] LoadMore
• [ ] NavLinks
• [ ] Spinner
• [ ] TopBar

[b5]

I'm hijacking this issue to plan our Store We’re going to be overhauling our UI & UX in the coming months, and we really want to get something like storybook in place before we start code work. This would give us an environment to experiment with & extend components & a place to iterate on different flows.

I'd like to structure this as a collaborative project that spreads across a few PRs, starting with one bigger PR that introduces a storybook to our codebase with a simple story around our existing Button component.

After that PR the next step would be to turn our Stylesheet component into story, and remove the Stylesheet component. Those two PRs should be enough to close this issue, we can make others for stories we'd like to see created once we better understand "story writing".

@ramfox feel free to chime in with your notes if you have any

PR1: Steps to complete:

• follow https://storybook.js.org/docs/guides/guide-react/
  • manually add the storybook dep to our dev dependencies
  • add an entry to package.json scripts, as outlined in the
  • follow the steps for adding a simple button, but use our button component instead
• add a new section to README.md called "Qri Storybook" linking to what the storybook is, and give quick steps to open the storybook
• open PR & 🎉

PR2:

• if PR1 isn't merged, branch off of that branch to add PR 2.
• port the contents of our current Stylesheet.js component over to a story, focusing on getting the contents of the render method into a form storybook is happy with
• delete the Stylesheet.js
• open PR2 & 🌮 🍕

@jlwaugh you'd mentioned interest in kicking this project off. We'd be happy to have you take point on PR 1 & 2 if you're up for it, then others can pile on with additional stories 😄.