feat(browser): introduce expect.element method and bundle jest-dom matchers with @vitest/browser

[sheremet-va]

Description

This PR adds expect.element(element) method which is a shorthand for expect.poll(() => element), but it requires Element:

await expect.element(div).toHaveTextContent('Hello World!')

The main reason why this API exists is to make retriability easier and more intuitive to manage. Previously, the most performant way was to get the element and pass the reference to poll which makes it verbose and not intuitive:

const input = screen.getByRole('input')
await expect.poll(() => input).toHaveValue('')

If you have it like this, the getBy is called multiple times which might be slow depending on the DOM state and the query itself:

await expect.poll(() => screen.getByRole('input')).toHaveValue('')

This PR also bundles jest-dom matchers for Vitest browser mode. I hope we can just import them in the future without the bundle process.

To have types recognize these, users need to add @vitest/browser/providers/playwright or @vitest/browser/providers/webdriverio to their tsconfig file.

TODO:

• Docs

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

• It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
• Ideally, include a test that fails without this PR but passes with it.
• Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Tests

• Run the tests with pnpm test:ci.

Documentation

• If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

• Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.