(feat): jest/vitest like API mocking

[christian-bromann]

This implements suggestion 2 from #252

TODO:

• Remove existing API access
• Update type documentation
• Update README

[goosewobbler]

You may be able to fix the CI error by moving the .npmrc from example-cjs into the root...

[goosewobbler]

Looks good, tests and types need to be improved, I'll make some changes in #269

[goosewobbler]

You may be able to fix the CI error by moving the .npmrc from example-cjs into the root...

This worked.

[goosewobbler]

Targetting a major release for this because the mocking interface has now changed completely. Removing the existing API access code will also improve unit coverage as some parts of it were not covered.

[christian-bromann]

This looks all great, nice work 👌

Let's update the mocking docs and emphasize the importance of using update to get the latest mock data.

I am wondering if there is any way we can auto-update it, e.g. fetch mock updates in the afterCommand hook to ensure that hooks are up to date after an interaction with the app. Anyway that should not block this PR to get merged. We could also think about calling update in our expect lib but that would couple these two packages which is not ideal.

[goosewobbler]

Makes sense, created #311 for this work. I'll update the docs tomorrow which should enable a release.

[christian-bromann]

@goosewobbler PR looks good, are we adding the two remaining todos to it?

[goosewobbler]

Yeah, just doing them now...

[christian-bromann]

Awesome work @goosewobbler 🎉 Thanks a lot!