chore: use Storybook for interaction tests instead of Playwright

[HeartSquared]

Why

KDS-1568

Playwright tests rely on a successfully deployed Storybook, but we have found that our branch previews deployed to AWS have at time been flaky (the contents reference will be incorrect, therefore have nothing loaded).

What

• Install Storybook testing suite and storybook/test-runner
• Convert our Playwright tests to either Jest or Storybook interaction tests (essentially Playwright tests under the hood)
• Extend our Chromatic workflow to run our interaction tests based on the deployed Chromatic branch
  • While it appears that the new workflow takes a lot longer than the old Playwright flow, it is because we now test all 400+ stories, whereas Playwright used to only have 19 tests
• Separate the PR and main branch Chromatic workflows (they have different intended workflows)
• Remove Playwright and associated config

[changeset-bot]

🦋 Changeset detected

Latest commit: eae0efe

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 0 packages

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

✨ Here is your branch preview! ✨

• Storybook

Last updated for commit 1596c0a: ci: add descriptions to workflows