Add an option to disable TLS cert validation for Rsc cmdlets with RSC-P (Private) deployments

[pasikarkkainen]

Rubrik (SaaS) hosted public RSC instances have a valid TLS cert signed with a public CA, but the privately hosted RSC-P instances instead have a self-signed TLS cert as a default.

"Connect-Rsc" is not able to connect to these RSC-P instances, giving an error such as:
VERBOSE: [Connect_Rsc] Authenticating ClientID client|client-id with RSC at https://rscp01.domain.tld/ . Connect-Rsc: One or more errors occurred. (The SSL connection could not be established, see inner exception.)

It would be good to have an option (environment variable) which can be used to disable the TLS cert validation, when needed, so that it's possible to connect to and use RSC-P instances out-of-the-box.

Obviously one can add a trusted public TLS cert to RSC-P, and/or setup a reverse proxy with a valid TLS cert, but anyway it would be good to be able to work with the RSC-P instances out-of-the-box by setting an environment variable for Rsc PowerShell cmdlets.