cargo upgrade is inconsistent with cargo

[epage]

Normally, cargo commands have the following flags to control which packages are selected

• --workspace to select all workspace members
• --pkgid to select specific packages in a workspace
• --exclude to de-select specific packages in a workspace

cargo upgrade instead has

• --workspace normal
• --pkgid normal
• --exclude instead this is selecting which dependencies to not upgrade, the opposite of the positional arguments

cargo update follows the standard model by the selector flags control selecting packages in the lock file to upgrade.

Other precedence:

• poetry doesn't have bulk upgrading yet, see Suggestion: new command to bump versions of dependencies in pyproject.toml python-poetry/poetry#461
• For yarn and pnpm, its unclear to me whether they are more like cargo update or cargo upgrade and if there is any precedent we can pull from

[epage]

cargo outdated uses the -i / --ignore flag

See https://crates.io/crates/cargo-outdated

[epage]

#785 fixed this by removing manifest selection