[FE/BE] Personalization: Technical discovery with yarn workspace

[DanielMiller-agile6]

Now that cross-app dependencies are removed from /personalization folder in vets-api, we can experiment with a yarn workspace.

A good, first potential use-case for this might be to manage our own little Storybook (or Ladle or other as team prefers) environment for workshopping and testing UI components in isolation, without requiring an api backend or integration with the va.gov website. This can often help FE developers when developing, testing and maintaining custom components (or unique applications of design system components) by providing a space to quickly spin up an environment to play with individual slices of the full UI pie.

This ticket should assess feasibility, and (ideally) be demo-able in a branch upon completion.

Some things to consider:

• webpack and compiler configs should match "real world" va.gov configs enough to trust our environment. can we reuse any webpack configs from platform for our own storybook environment?
• if other teams were to use storybook in this way, will our storybooks be appropriately isolated? could we potentially combine all teams' Storybooks into one big version and deploy somewhere for observability?
• will our version of node/npm be a problem? we'll likely need to use an older version of Storybook to sync up with vets-website dependencies

Acceptance criteria

• [ ] Create a POC with storybook or look at other options: https://ladle.dev/ is one Adam knows of that is similar to storybook
• [ ] If storybook isn't a viable thing to try, then try adding a well vetted dependency to the mix and try it out. Maybe something like RTK (redux toolkit) or React Query that could be a good fit to ease engineering burden? What other libraries might make our job easier and adding them would have a minimal impact on exiting codebase?

[ACParker89]

@DanielMiller-agile6 do we need this still?