win_chocolatey - Improve docs around install_args and package_params

[vexx32]

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

The documentation around install_args and package_params is not particularly clear as to when one should be used over the other.

install_args:

chocolatey-ansible/chocolatey/plugins/modules/win_chocolatey.py

Lines 111 to 117 in 85ee7fd

	install_args:
	description:
	- Arguments to pass to the native installer.
	- These are arguments that are passed directly to the installer the
	Chocolatey package runs, this is generally an advanced option.
	type: str
	version_added: '0.2.1'

package_params:

chocolatey-ansible/chocolatey/plugins/modules/win_chocolatey.py

Lines 133 to 141 in 85ee7fd

	package_params:
	description:
	- Parameters to pass to the package.
	- These are parameters specific to the Chocolatey package and are generally
	documented by the package itself.
	- Before Ansible 2.7, this option was just I(params).
	type: str
	version_added: '0.2.1'
	aliases: [ params ]

Describe The Solution. Why is it needed?

This came up in the Chocolatey Discord, a user was trying to use install_args to pass package parameters, as the documentation around these two options is not super clear.

Quote:

I wish that would be a bit clearer in the ansible docs, the phrase "Parameters to pass to the package." there was not for me clear as "MSI Properties" in the package page.

We should likely pull from Chocolatey's own command/option documentation and make the difference between these much more evident. Users should be able to infer from the options documentation that when passing parameters to a package install script, they should be using package_params, and when passing custom parameters to the underlying MSI/EXE/etc that a package might be running, they should be using install_args.

Additional Context.

N/A

Related Issues

N/A