Smoke test release candidate

[klippx]

Problem

Fixes #408

Solution

This PR smoke tests a release to ensure the npm artefact is ready for release. The steps are roughly:

1. Clone repo, install deps
2. Prepare a mappersmith release
3. Clone https://github.com/klippx/mappersmith-consumer repo
4. In mappersmith-consumer: Link to the release candidate
5. In mappersmith-consumer: Run all test scripts verifying that they run with release candidate

Impact

• This ensures that consumer projects are not broken*
• If there is a missed case it is easy to add to that as a new workspace consumer project
• No impact on this project in terms of deps

*) to the extent that we know about it and that it is documented, of course

[changeset-bot]

⚠️ No Changeset found

Latest commit: bd9ff52

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR