Description

This PR improves the Storybook configuration to be more flexible and inclusive, allowing stories to be created anywhere within the app/ directory structure. Previously, stories were limited to specific component library directories, which prevented the creation of stories for Base components and other UI elements outside the design system.

Changelog

CHANGELOG entry: Improved Storybook configuration to allow stories from any app directory and added Keypad component story

Related issues

Fixes: N/A
Improvement: Enables better component development workflow by allowing stories for Base components and other UI elements

Manual testing steps

1. Run yarn storybook-generate to ensure story detection works
2. Launch the app in Storybook mode
3. Navigate to "Base Components / Keypad / Default" in Storybook
4. Verify the Keypad story renders correctly with interactive functionality
5. Test that existing component library stories still work as expected
6. Confirm that stories can now be added to any component in the app/ directory

Screenshots/Recordings

Before

• Stories were limited to component-library/components, component-library/base-components, and component-library/components-temp directories only
• Keypad component had no isolated development environment

After

• Stories can be created anywhere in the app/ directory structure
• Keypad component now has a dedicated story for isolated development and testing
• More flexible configuration supports future story additions across the entire app

Pre-merge author checklist

• I've followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• 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.