chore(scripts): Use relaxed peer dependencies to avoid triggering major version bumps

[chaance]

Consider this scenario:

1. Run yarn changeset:version to bump versions
2. Changesets sees that a package has a minor change
3. Because we release packages in lockstep, all packages get a minor update
4. @remix-run/dev has "peerDependencies": { "@remix-run/serve": "1.8.0" }
5. This dependency will now be out of range after the update
6. Changesets makes the safe bet and updates @remix-run/dev to 2.0.0 because it can't be sure this doesn't result in a breaking change
7. Because we release packages in lockstep, all packages get a major update

In practice, this means any minor changeset will result in a major bump, which definitely isn't what we want. This means I end up manually updating all of the package versions which ... kinda sucks.

Instead, we relaxe the peer dependency range for internal packages. That way the update doesn't result in an out-of-range peer dependency, and all packages are bumped to the next minor release instead.

Because changesets doesn't automatically bump peer dependencies with the relaxed range (which makes sense in most cases), I added a script does that for us. This makes the change safer because updating the leading dependency will result in a peer dependency warning if the user doesn't bump the peer dependency for some reason.

Thanks to @Andarist for the guidance here and the original script!

[changeset-bot]

⚠️ No Changeset found

Latest commit: 908f826

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

[Andarist]

Because changesets doesn't automatically bump peer dependencies with the relaxed range (which makes sense in most cases)

I wouldn't say that this makes sense in most cases though. It's a contextual decision. For example, it's not a good default for Babel plugin (usually they depend on ^7) or UI kit libraries with a peer dep on a framework (when depending on React you might want to depend on a version with a certain feature, like if you depend on hooks then u stay on the ^16.8 range).

I think though that this strategy makes sense in your case.

[chaance]

I wouldn't say that this makes sense in most cases though. It's a contextual decision. For example, it's not a good default for Babel plugin (usually they depend on ^7) or UI kit libraries with a peer dep on a framework (when depending on React you might want to depend on a version with a certain feature, like if you depend on hooks then u stay on the ^16.8 range).

Updated the inline comment as not to sully your good name 😀