Jest Augmentations Limitations

As discovered while working on this PR, here are the issues to document the limitations around augmentation usage.

See the augmentation issue for Jasmine there https://github.com/webdriverio/expect-webdriverio/issues/1893

Jest

1. As documented here and demonstrated in this project, we can utilize Jest with @jest/globals and @types/jest to use Jest's expect with wdio augmentation, but it is not a plug-and-play, out-of-the-box solution.
2. As shown here, to use Jest’s augmentation, we also need to register the wdio custom matcher manually.
3. Additionally, to utilize the soft assertion service, we need to register it, as shown here.
4. The typing @types/jest is not offered and supported by Jest’s maintainer, and there is a long-standing issue around that here to get rid of @types/jest
5. When using Jest’s augmentation of the wdio matchers toMatchSnapshot and toMatchInlineSnapshot, they conflict with one of Jest’s.
6. A workaround to avoid requiring the registration of the wdio matcher & soft assertion is to force the global.expect (as shown here) to be one of the wdio options, but this could also break other parts of a monorepo project.

Read the linked PR #1863 and Jasmine augmentation issue #1893, then review the referenced Jest boilerplate setup examples. Document the listed Jest augmentation, matcher-registration, soft-assertion, typing, snapshot-conflict, and global.expect limitations; done means these limitations and workarounds are covered in the repository documentation.