New/Set-CcmDeploymentStep should have parameters for -AllowPrerelease and -Version for basic steps

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

CCM v0.10.0 added functionality for Basic deployment steps to include additional parameters, namely `--pre` and `--version`. The `*-CCMDeploymentStep` commands do not currently have functionality for these parameters.

## Describe The Solution. Why is it needed?

Add extra parameters to the `Basic` parameter set for these commands and ensure they are passed into the API correctly.

API expects the additional parameters to be provided as part of the `script` value in the JSON input, so the format is now `$ChocoCommand|$PackageName|$Version|$AllowPrerelease` (although I believe omitting the latter two portions entirely is acceptable for backwards compat reasons if neither needs to be provided?)

## Related Issues

- #64
- #63

Start by locating the New-CCMDeploymentStep and Set-CCMDeploymentStep commands and their Basic parameter sets. Trace how the existing script value is assembled and sent to the API, then verify that -Version and -AllowPrerelease are represented in the expected pipe-delimited format while existing usage remains compatible.

Written by the indexing model from the issue text.