Better soft assertions support

[dprevost-LMI]

Soft assertions currently have three limitations:

1. It does not support basic matchers like toBe or toEqual from the expect library, but only custom matchers of wdio. This line is related.
2. If we support the above, the current implementation uses await by default, which is not required when called for basic matchers. See this code line.
3. When using Jasmine augmentation, the soft assertions method is not available in the typing. See jasmine.d.ts

• Also, if jasmine is used as the global ambient soft is not working vs if we import expect from expect-webdriverio. However, this is potentially a @wdio/jasmine-framework or @wdio/local-runner bugs and not one from expect-webdriverio

To expand a bit

1. matchers from import { matchers } from './index.js' only contains custom matcher. Removing it allows us to expand to more matchers, but also removes "the checks"
2. Depending on whether the matcher is expecting void or Promise<void>, we should somehow fork the code to await or not. However, how can we achieve that?
3. See the two screenshots below taken using this project: https://github.com/dprevost-LMI/jasmine-boilerplate/tree/test-latest-expect-webdriverio_jasmine-expectAsync

When Jasmine is the global ambient, the functions are not registered when used with @wdio/jasmine-framework and @wdio/local-runner, and globally, we need to explicitly use import { expect } from 'expect-webdriverio' to have it working

Unavailable typing on jasmine augmentation (maybe something we do not want to support, though)

[christian-bromann]

Thoughts @JustasMonkev?

[JustasMonkev]

Yeah, you're right. I never tested with basic matchers like toBe/toEqual or checked Jasmine properly. The matchers.has() check is too limiting and the unnecessary awaits are problematic.
Good catches - these need fixing. @christian-bromann @dprevost-LMI

[dprevost-LMI]

3. When using Jasmine augmentation, the soft assertions method is not available in the typing. See jasmine.d.ts

I learned that Jasmine is designed by default to behave like a soft assertion and to handle errors only at the end of the test, on top of any non-awaited promises. Therefore supporting soft assertion does not seem to be a real concern