Update crayons components to use Storybook as single source of truth

[aitchiss]

Our storybook has been getting lots of great updates recently, and as we invest more in it, we want to make sure it's our single source of truth for design-system component documentation. However, a few components still have JSDoc comments either as duplication or instead of comprehensive storybook docs. I'm also including in the list below components that appear in Storybook but don't have docs at all.

For each of these components, we should:

• Make sure the Storybook docs tab has comprehensive information on the component
• Make sure relevant prop types are documented in Storybook in the controls tab
• Once we're satisfied with those two things... delete the JSDoc comments!

I had a quick look, and these are the components I think we need to look at:

• TagAutocompleteOption
• LoadingArticle
• Article
• CommentSubscription
• MarkdownToolbar
• MentionAutocompleteTextArea
• PodcastEpisode
• Snackbar
• ButtonGroup
• Dropdown
• Checkbox
• RadioButton

Some of these have some existing docs or prop controls in Storybook, but most are missing one or the other.

We can address these docs updates in small incremental PRs - one per component

[github-actions]

Thanks for the issue, we will take it into consideration! Our team of engineers is busy working on many types of features, please give us time to get back to you.

Feature requests that require more discussion may be closed. Read more about our feature request process on forem.dev.

To our amazing contributors: issues labeled type: bug are always up for grabs, but for feature requests, please wait until we add a ready for dev before starting to work on it.

To claim an issue to work on, please leave a comment. If you've claimed the issue and need help, please ping @forem/oss. The OSS Community Manager or the engineers on OSS rotation will follow up.

For full info on how to contribute, please check out our contributors guide.

[EKivutha]

@aitchiss please assign this issue

[citizen428]

@EKivutha I assigned you the issue now, thanks for volunteering.

[aitchiss]

Thanks for taking on this issue @EKivutha - just a reminder to submit any changes for this as small incremental PRs, ideally component by component. This will help keep things straightforward to review 🙂

[EKivutha]

Noted @aitchiss