chore: adding github workflow to publish storybook react

[georgewrmarshall]

Description

This PR adds GitHub Actions workflow to automatically build and deploy the Storybook React to GitHub Pages whenever changes are merged to the main branch.

• Triggers on pushes to main branch
• Uses the official github actions actions/upload-pages-artifact@v3 and actions/deploy-pages@v4 as suggested in this comment
• Doesn't require a secret because official actions use GitHub's built-in OpenID Connect (OIDC) authentication.

Related issues

Fixes: #3

Manual testing steps

The action has been successfully tested(again) in a fork environment. You can see the working deployment at georgewrmarshall.github.io/metamask-design-system

1. Merge this PR to main branch
2. Wait for the GitHub Action to complete (~2-3 minutes)
3. Visit https://metamask.github.io/metamask-design-system/ to verify Storybook is deployed

Screenshots/Recordings

Before

N/A - No previous Storybook deployment

After

• Successfully deployed Storybook: Fork Demo
• GitHub Action running successfully in fork environment

after480.mov

Technical Implementation Details

• Workflow uses workspace-aware commands to build dependencies
• Correctly handles monorepo structure with appropriate working directory settings
• Uses relative paths for GitHub Pages deployment to ensure compatibility
• Maintains proper build order: tokens → tailwind preset → react components → storybook

Pre-merge author checklist

• I've followed MetaMask Contributor Docs
• I've completed the PR template to the best of my ability
• I've included tests if applicable
• I've documented my code using JSDoc format if applicable
• I've applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

[georgewrmarshall]

After further inspection I'm not sure this action will work the same as it did in the design tokens repo. Will try forking the repo

Update: I forked our repo and the action is now working you can see the deployed fork at georgewrmarshall.github.io/metamask-design-system

[itsyoboieltr]

I would remove cache-node-modules and try to use the official github action for deployment if possible.