bump unstable versions by at least a patch

[mansona]

I was having some issues where pnpm was picking up some wrong versions during an ember-try run and I was pulling my hair out 🙃

I noticed that @embroider/compat version 2.1.1 was being used instead of the version 2.1.1-unstable.00ec2e7 that was specified in the package.json. No matter what I did I couldn't get pnpm to pick up correct version. Then I noticed that we're using carat dependencies in the package json on ember-try ever since #1328 and that seems to have caused my issue.

Apparently the version ^2.1.1-unstable.00ec2e7 is satisfied by 2.1.1 😭

This PR will make sure that all new packages that are deployed with the unstable packages will be at least one step higher and won't match any more

[NullVoxPopuli]

I didn't believe it, but here we are: https://runkit.com/nullvoxpopuli/semver-satisfies-unstable

const semver = require('semver');

const unstable = `2.1.1-unstable.00ec2e7`;
const stable = `2.1.1`;
const range = `^${unstable}`;

console.log(`does ${stable} satisfy range: ${range} :: ${semver.satisfies(stable, range)}`);

(prints true)

If we change the version around so that semver.corce doesn't drop the -unstable tag, unstable-00ec2e7_2.1.1, we get an expected false -- I don't recall if this is a valid version on npm though (I would be surprised if it is)

[NullVoxPopuli]

We could also get rid of the ^, and that works + also feels less complex: https://runkit.com/nullvoxpopuli/semver-satisfies-unstable

"does 2.1.1 satisfy range: ^2.1.1-unstable.00ec2e7 :: true"
"does 2.1.1 satisfy range: ~2.1.1-unstable.00ec2e7 :: true"
"does 2.1.1 satisfy range: 2.1.1-unstable.00ec2e7 :: false"

[NullVoxPopuli]

Discussed on the call today, and there is more to do (esp around test-setup capabilities), but those things can be separate PRs! 🎉

nice work!!