Converting from testing-library to vitest API

[kwojcik]

Wanted to share a neat prompt for converting from testing-library tests to the new vitest API. I first started writing an autofix lint rule to do this, but I quickly realized that would have to cover too many cases. This prompt works pretty well in copilot to convert tests, maybe you need to add more info to the prompt to handle some quirks of your specific use cases.

Convert this test to use the Vitest interactivity API described here https://vitest.dev/guide/browser/interactivity-api.
* Do not use `screen`
* Use `page` from `'@vitest/browser/context'`
* `expect` typically needs to be converted to `expect.element` and awaited. 
* The `*allBy*` locators do not exist in vitest. You must use `getBy*`, and if it's going to find multiple elements then use `.all()` to access an array of found elements.
* You can click an element by calling `.click()` on it; you do not need to use `userEvent.click`
* `queryBy*` does not exist; use `getBy*`
* Locators should not be awaited, eg do not do `const button = await page.getByRole(...)`
* Elements which should not exist should be asserted with `expect.element(e).not.toBeInTheDocument()`
* You do not need to assert visibility before clicking something, this is sufficient eg `await page.getByRole('button').click()`
* In the old code, `await screen.findBy*(...);` on its own is an implicit visibility assertion. That needs to be converted to `expect.element(page.getBy*(...)).toBeVisible();`
* In the old code, `.toHaveClass()` takes multiple arguments, but in vitest it takes a single argument of a space-separated string. Eg `toHaveClass('a', 'b')` should become `toHaveClass('a b')`
* example/path/to/test.ts is an example file that has been converted.