refactor: update Storybook docs and usage

[TylerAPfledderer]

Description

This PR updates the applying-storybook docs to match the latest usage of Storybook, and updates existing stories to match said usage.

This PR recognizes that these docs and approach to using storybook for the project might be considered fluid as implementation of the new DS still continues, and further contributions from the community can alter the approach in the future for improved DX.

Related Issue

N/A

[gatsby-cloud]

✅ ethereum-org-website-dev deploy preview ready

• Deploy preview
• Build logs · 30m build time

[netlify]

✅ Deploy Preview for ethereumorg ready!

Name	Link
🔨 Latest commit	f74fbbf
🔍 Latest deploy log	https://app.netlify.com/sites/ethereumorg/deploys/66077b5499c7020008c147c7
😎 Deploy Preview	https://deploy-preview-11324--ethereumorg.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[wackerow]

@TylerAPfledderer For my own understanding, is there any need/benefit to match the text in these stories (ie a label, or children text) to the text found in the Figma DS components?

---

This otherwise looks good to me! Thanks so much for cleaning this up... gonna add one commit to capitalize "Figma", but otherwise think we can pull this in. 💪

[TylerAPfledderer]

For my own understanding, is there any need/benefit to match the text in these stories (ie a label, or children text) to the text found in the Figma DS components?

@wackerow I would argue that doing this would make it helpful for Nuno with consistency in verifying the design has been implemented to code as intended. Applying some other content may bring out an edge case or an underlying bug with widths or spacing, but also using the content from Figma would provide a true baseline in the conversion to the Storybook visual testing environment.

Side note: "consistency" seems to be the unfortunate buzzword for me 🤣

[wackerow]

Merged... thanks @TylerAPfledderer! I agree that we should strive to match the text to Figma where possible, especially on the base components. Can address that separate from this.