fix: Update semver logic

[kschlarman]

Summary

Update compatibility logic to coerced versions to valid semver (e.g 4.17.1-runtime.7 -> 4.17.1).

---

For us to review and ship your PR efficiently, please perform the following steps:

• Open a bug/issue before writing your code 🧑‍💻. This ensures we can discuss the changes and get feedback from everyone that should be involved. If you`re fixing a typo or something that`s on fire 🔥 (e.g. incident related), you can skip this step.
• Read the contribution guidelines 📖. This ensures your code follows our style guide and
  passes our tests.
• Update or add tests (if any source code was changed or added) 🧪
• Update or add documentation (if features were changed or added) 📝
• Make sure the status checks below are successful ✅

A picture of a cute animal (not mandatory, but encouraged)

[conventional-commit-lint-gcf]

🤖 I detect that the PR title and the commit message differ and there's only one commit. To use the PR title for the commit history, you can use Github's automerge feature with squashing, or use automerge label. Good luck human!

-- conventional-commit-lint bot
https://conventionalcommits.org/

[eduardoboucas]

🚀

[ascorbic]

Suggested change

	versions.find(({ version }) => semver.satisfies(semver.coerce(version), pinnedVersion)) || {
	versions.find(({ version }) => semver.satisfies(version, pinnedVersion, { includePrerelease: true })) || {

This should work