fix: remove unused --save option for set resolution command

[akwodkiewicz]

The option was never implemented in berry, but it's mentioned in the docs as well as in the CLI output.

I don't have the expertise to actually implement the flag, so the second best thing to do here is to remove it, so that people are no longer mislead.

What's the problem this PR addresses?

Mitigates #2202 (actual resolution should be implementing the flag).

How did you fix it?

Removed unnecessary flag.

Checklist

• I have read the Contributing Guide.

• I have set the packages that need to be released for my changes to be effective.

• I will check that all automated PR checks pass before the PR gets reviewed.

[akwodkiewicz]

I am not completely sure if there should be some other packages bumped as well. Is upgrading only @yarnpkg/plugin-essentials ok, or should I upgrade also all/some other packages as well?

[clemyan]

You need to bump @yarnpkg/cli too because the default plugins are bundled into it

[akwodkiewicz]

@clemyan, what about ~15 packages that depend on @yarnpkg/cli? Do they have to be bumped as well?

Depending on your answer I'll have to either decline or bump those packages, because
f911b7f is only bumping @yarnpkg/cli and leaving the rest as "undecided".

[clemyan]

what about ~15 packages that depend on @yarnpkg/cli? Do they have to be bumped as well?

You can leave those as declined.

The reason you need to bump @yarnpkg/cli is because the code for all default plugins are included and bundled into the @yarnpkg/cli. So in order for users to see your changes, a new version of the CLI needs to be released.

Most other workspaces only have dev dependency on @yarnpkg/cli. The only workspaces that have a prod dependency on it are @yarnpkg/doctor and @yarnpkg/builder, but neither are affected by this change.

[akwodkiewicz]

Awesome, thank you very much for the thorough explanation 👍