Packages used for testing should meet Chocolatey Community Repository validation minimums

### Checklist

- [x] I have verified this is the correct repository for opening this issue.
- [x] I have verified no other issues exist related to my request.

### Is Your Feature Request Related To A Problem? Please describe.

Currently, there are a number of package files in this repository that do not match the requirements of the[Chocolatey Community Validation Extension](https://community.chocolatey.org/packages/chocolatey-community-validation.extension).

This causes problems when attempting to test/use/alter these packages, as attempts to `choco pack` these packages fail. This is due to the fact that most people on the team, and who are contributing to this repository, have this extension installed.

We should follow our own guidelines, and ensure that all packages meet the minimum recommendations, even though they are _just_ test packages.

### Describe The Solution. Why is it needed?

All the test packages that are stored in the repository need to be updated to ensure that the nuspec files are meeting the requirements as laid down by the [Chocolatey Community Validation Extension](https://community.chocolatey.org/packages/chocolatey-community-validation.extension).

Once an issue is identified, it should be a case of fixing the issue across multiple files, so it _should_ be a relatively painless process, just repeating the change in multiple places.

@corbob has started some of that work [here](https://github.com/corbob/choco/commits/maint-standardize-test-packages/).

### Additional Context

N/A

### Related Issues

- Internal 868a48c53

Start by reviewing the test package nuspec files and the Chocolatey Community Validation Extension requirements, then use choco pack to identify validation failures. Update the affected package files consistently, and confirm that all test packages can be packed without validation errors.

Written by the indexing model from the issue text.