feat(expect): add toSatisfy asymmetric matcher

[hi-ogawa]

Description

I just noticed jest-extended has this https://jest-extended.jestcommunity.dev/docs/matchers/toSatisfy Note that we already have assertion form expect(...).toSatisfy(...) (which uses chai's `.to.satisfy), but there wasn't asymmetric matcher.

One use case this would help is for error assertions like mentioned in

• How to check if toThrowError is throwing an error with specific properties? #4378
• toThrowError() Does Not Support Custom Error Types #4559

expect(someFnToThrowError).toThrow(expect.toSatisfy((e) => {
  expect(e).toBeInstanceOf(MyError);
  // ...
  return true;
}))

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:.

[netlify]

✅ Deploy Preview for vitest-dev ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	13a0b89
🔍 Latest deploy log	https://app.netlify.com/sites/vitest-dev/deploys/67525ac4429b8b0008bd043c
😎 Deploy Preview	https://deploy-preview-7022--vitest-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[sheremet-va]

Asymmetric matchers are added automatically if the new assertions is extended with expect.extend - maybe we can do that instead of writing new matchers all the time?

expect.extend({
  toSatisfy() { /* ... */ }
})
expect(22).toSatisfy(() => 22)
expect(22).toEqual(expect.toSatisfy(() => 22))

[AriPerkkio]

This started to fail tests after merge to main 🤔

[sheremet-va]

Ah, it's because of #7043. We should also updated the diff here