ClientSetup Enhancements - Parameterize script to allow for additional flexibility

[ryanrichter94]

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.

Through customer interaction these are the nice additions we feel would be well received to edit within ClientSetup

• Allow entry of Passing domain credential for agent installation
• Allow toggle of ContextMenu on or off with extension install
• Make adding additional packages to ClientSetup easier
• Make adding additional chocolatey sources easier

Describe The Solution. Why is it needed?

These enhancements would make the ClientSetup script more flexible by providing parameters to the script to support more customizable installs.

Additional Context

No response

Related Issues

No response

[steviecoaster]

This could be done with additional parameters:

[Parameter()]
[Hashtable[]]
$AdditionalPackages,

[Parameter()]
[Hashtable[]]
$AdditionalConfiguration

We could then just act on it at the end of ClientSetup:

if($AdditionalPackages){
  #action here
}

if($AdditionalConfiguration){
  #Action here
}

[JPRuskin]

If doing AdditionalPackages can I suggest that we trigger the Jenkins job (like we do in Azure / Ansible) rather than adding further logic?

See: https://github.com/chocolatey/c4b-azure/blob/main/source/Initialise-C4B.ps1#L174-L184