(multiple) Remove unsupported reference on Chocolatey CLI

[AdmiringWorm]

Description

This updates the references for packages that requires a specific version of Chocolatey CLI, to remove those references that required a version that we no longer support.

Motivation and Context

We do not want to keep referencing Chocolatey CLI when the required version is one that we no longer support. At the time, the earliest version we support is 1.3.0.

How Has this Been Tested?

No functional changes has been made, and as such has not been tested through the Chocolatey Test Environment.

Screenshot (if appropriate, usually isn't needed):

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [x] Breaking change (fix or feature that would cause existing functionality to change)
• [ ] Migrated package (a package has been migrated from another repository)

Marked as a breaking change, as it techhnically is. However, it is a breaking change introduced by cleaning up packages.

Checklist:

• [x] My code follows the code style of this repository.
• [ ] My change requires a change to documentation (this usually means the notes in the description of a package).
• [ ] I have updated the documentation accordingly (this usually means the notes in the description of a package).
• [ ] I have updated the package description and it is less than 4000 characters.
• [x] All files are up to date with the latest Contributing Guidelines
• [ ] The added/modified package passed install/uninstall in the Chocolatey Test Environment(https://github.com/chocolatey-community/chocolatey-test-environment/). Note that we don't support the use of any other environment.
• [ ] The changes only affect a single package (not including meta package).

[AppVeyorBot]

:x: Package verification failed, please review the Appveyor Logs and the provided Artifacts before requesting a human reviewer to take a look.

[AdmiringWorm]

The failure is expected, as the updater is currently broken for some of these packages.

[gep13]

@AdmiringWorm said... The failure is expected, as the updater is currently broken for some of these packages.

Agreed. Going to proceed with merging this.