Adding module mocking to the storybook based on __mocks__ directory
What does this MR do and why?
Based on #450450 (closed) and !146499 (merged) I prepared a proof of concept for mocking modules in the storybook. Any module in the application can be mocked here by just creating a module in the ROOT_DIRECTORY/storybook/__mocks__/filePath
where the file matches path with the module it's mocking ROOT_DIRECTORY/filePath
.
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
Just launch the storybook
Related to #450450 (closed)