[Bug]: Migrate @jest-playwright-preset to @playwright/test to avoid security issue.

[Leah-Xia-Microsoft]

Describe the bug

@jest-playwright-preset is not getting maintained anymore. See:
https://github.com/playwright-community/jest-playwright?tab=readme-ov-file#%EF%B8%8F-we-recommend-the-official-playwright-test-runner-playwrighttest-%EF%B8%8F
And it's using a dependency that's using axios <1.7.4. which is causing a security issue that's fixed in a later version. (jeffbski/wait-on@672fd83)
The suggestion from the @jest-playwright-preset team is to migrate to @playwright/test.
Migration should be pretty straightforward, following https://playwright.dev/docs/intro

To Reproduce

No repro step needed.

System

Any system

Additional context

No response

[501NotImplemented]

Also would like to add that completing this ticket would help to resolve the issue when playwright package is not found that occurs after the direct playwright package was deprecated by PW team in favor of using the @playwright/test.

[yannbf]

Hey everyone! Migrating away from jest-playwright-preset is not a simple task. It takes care of many things, which would need porting. PRs are welcome, but we don't have plans at the moment for doing this kind of work.

If you're using Vite in your project, please consider checking out this blog post on our new way to run tests in Storybook using Vitest!

[prewk]

I'd like to just add to this: Migrating away from jest-playwright-preset will help clean up the big clutter that happens when you install Storybook's test runner while you simultaneously have playwright as your normal e2e browser testing framework. You sort of get playwright twice right now, with all that it entails.