Add Unit test to cover New storage Context in different RMprofile and SMProfile combination

[blueww]

Description

Add Unit test to cover New storage Context Test in different RMprofile and SMProfile combination.

We have a severe regression issue in the latest stage of release 4.0.0, which is not caught by Unit test.
#3939

Mark has add test coverage for this issue in #3938 .
But #3938 only cover the RMprofile!=null and SMProfile=null scenario, So this PR add all combination to avoid regression .

This checklist is used to make sure that common guidelines for a pull request are followed. You can find a more complete discussion of PowerShell cmdlet best practices here.

• [ Y] I have read the contribution guidelines.
• [Y ] If changes were made to any cmdlet, the XML help was regenerated using the platyPSHelp module.
• [ Y] If any large changes are made to a service, they are reflected in the respective change log.

General Guidelines

• [ Y] Title of the pull request is clear and informative.
• [ Y] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.
• The pull request does not introduce breaking changes (unless a major version change occurs in the assembly and module).

Testing Guidelines

• [ Y] Pull request includes test coverage for the included changes.
• [ Y] PowerShell scripts used in tests should do any necessary setup as part of the test or suite setup, and should not use hard-coded values for locations or existing resources.

Cmdlet Signature Guidelines

• [ Y] New cmdlets that make changes or have side effects should implement ShouldProcess and have SupportShouldProcess=true specified in the cmdlet attribute. You can find more information on ShouldProcess here.
• [ Y] Cmdlet specifies OutputType attribute if any output is produced - if the cmdlet produces no output, it should implement a PassThru parameter.

Cmdlet Parameter Guidelines

• [ Y] Parameter types should not expose types from the management library - complex parameter types should be defined in the module.
• [ Y] Complex parameter types are discouraged - a parameter type should be simple types as often as possible. If complex types are used, they should be shallow and easily creatable from a constructor or another cmdlet.
• [ Y] Cmdlet parameter sets should be mutually exclusive - each parameter set must have at least one mandatory parameter not in other parameter sets.

[blueww]

On Demand test: http://azuresdkci.cloudapp.net/view/1-AzurePowerShell/job/powershell-demand/1588/

[markcowl]

@blueww Please add any additional scenarios to the tests I added, as xunit tests. We are not accepting any new MSTest tests in the repo, and these need to be check-in tests

[blueww]

Thanks for the comments!
Will try to find some time to fix it.

[blueww]

The cases are added to the new test you added.
The PR is updated, please check.

[blueww]

New Demand test pass: http://azuresdkci.cloudapp.net/view/1-AzurePowerShell/job/powershell-demand/1609/

[markcowl]

Please either remove this test, or file an issue for fixing the underlying issue and reference the issue id here. The issue must be resolved by the end of the next sprint.

[blueww]

The case is removed, and new on demand test: http://azuresdkci.cloudapp.net/view/1-AzurePowerShell/job/powershell-demand/1617/

We will continue to following this in mail to see if this is a valid scenario. If so, we need fix it.

[markcowl]

@blueww one correction, otherwise LGTM

[markcowl]

on demand run here: http://azuresdkci.cloudapp.net/view/1-AzurePowerShell/job/powershell-demand/1619/