Cmdlets should respect SwitchParameter values not presence alone

[anamnavi]

Some parameter switches like -WhatIf, -PSGallery for certain cmdlets were not being checked and used logically in the correct manner. The previous code was simply checking if the parameter switch was supplied and if so, equating that to the value of the parameter switch being true. This meant that in a scenario like, -WhatIf:$false the code detected presence of the -WhatIf parameter and did not install the package. Now, switch parameter values are checked. For -PSGallery switch parameter in Register-PSResourceRepository providing -PSGallery:$false will mean PSGallery is not registered and no error is reported.

PR Summary

PR Context

Resolves #1805

PR Checklist

• PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• Summarized changes
• Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
• This PR is ready to merge and is not Work in Progress.
  • If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.
• Breaking changes
  • None
  • OR
  • Documentation needed
    • Issue filed:
• User-facing changes
  • Not Applicable
  • OR
  • Documentation needed
    • Issue filed:
• Testing - New and feature
  • N/A or can only be tested interactively
  • OR
  • Make sure you've added a new test if existing tests do not effectively test the code changed
• Tooling
  • I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
  • OR
  • I have considered the user experience from a tooling perspective and enumerated concerns in the summary.

[anamnavi]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).