Update AutoMapper to 6.0.2

[cormacpayne]

Description

Initial attempt at fixing issue #4294 by bumping the version of AutoMapper used and adopting a singleton pattern with the new version that will prevent the mapper from being populated every time a cmdlet is executed.

---

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.

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

General Guidelines

• Title of the pull request is clear and informative.
• 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

• Pull request includes test coverage for the included changes.
• 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

• 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.
• Cmdlet specifies OutputType attribute if any output is produced - if the cmdlet produces no output, it should implement a PassThru parameter.

Cmdlet Parameter Guidelines

• Parameter types should not expose types from the management library - complex parameter types should be defined in the module.
• 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.
• Cmdlet parameter sets should be mutually exclusive - each parameter set must have at least one mandatory parameter not in other parameter sets.

[cormacpayne]

Building packages job: http://azuresdkci.cloudapp.net/job/posh-pack/3/

[markcowl]

Just a couple of questiosn about AutoMapper.Net4 - it looks liek this was removed form the wxi file everywhere, but noted at least one palce there is still a reference. Want to make sure we understand why.

[markcowl]

So we don't need this file anymore?

[markcowl]

This looks like AutoMapper.Net4 is still used in some circumstances

[blueww]

@cormacpayne
I don't see the storage module code change in this PR (am I missing anything?)
And I don't quite understand how the fix works.
Could you please give more details on how the problem happens, and how the fix works?
Thanks!

[cormacpayne]

@blueww Hey Wei, the bulk of the Storage code changed is in the ServiceManagementProfile class, which defines the mappings for types used in RDFE cmdlets. It appears the issue that the user is seeing in #4418 comes from the code here - AutoMapper is trying to map an object of type StorageAccountGetResponse to StorageServicePropertiesOperationContext, but it cannot find a corresponding mapping (even though it's defined in the ServiceManagementProfile class).

Currently, AutoMapper is being used statically throughout the modules, which is why we believe these issues with "unsupported mappings" are popping up - the correct mappings may not have been instantiated by the time the mapper is used. This PR updates the version of AutoMapper used to 6.0.2, which deprecates the support of a static mapper, and we define a specific mapper to be used for each module. This ensures that every module has their own mapper, every call to Mapper.Map<Foo, Bar>() is using the module's specific mapper, and that the mapper is instantiated with the correct mappings whenever it is used.

Now, rather than calling Mapper.Map<Foo,Bar>() in the previously cited GetAzureStorageAccount class, you will now use the specific mapper that has defined the mappings you will need, ServiceManagementProfile.Mapper.Map<Foo,Bar>().

[cormacpayne]

On-demand: http://azuresdkci.cloudapp.net/job/powershell-demand/1914/

[cormacpayne]

On-demand: http://azuresdkci.cloudapp.net/job/powershell-demand/1917/

[cormacpayne]

@azuresdkci test this please

[cormacpayne]

@azuresdkci test this please

Approved offline pending compute signoff

[cormacpayne]

Received sign-off from Compute and Network that this does not break existing scenarios.