New-CCMDeploymentStep -Type parameter feels redundant

```ps1
$step = @{
Deployment = $Deployment.Name
Name = 'Choco Upgrade All'
TargetGroup = $Group.Name
# why is this here?
Type = 'Basic'
ChocoCommand = 'upgrade'
PackageName = 'all'
}
New-CCMDeploymentStep @step
```

I think the best way forward here is to remove the `Type` parameter completely (it's not really adding anything here) and just have the `-Script` or `-ChocoCommand` (and `-PackageName`) parameters be mandatory in their sets.

Start at the New-CCMDeploymentStep entry point and inspect how its Type parameter and parameter sets are defined. Check the existing command behavior and tests, if present; done means Type is no longer required or accepted, while Script or ChocoCommand with PackageName is mandatory in the appropriate sets.

Written by the indexing model from the issue text.