Edited New-AzVm to ensure the PlatformFaultDomain parameter in the VmConfig object is used

[Sandido]

Description

This bug was made showing that if a user was creating a VM attached to a Vmss with a VMConfig object, and the VM has a PlatformFaultDomain value, the PFD value was not put onto the created VM.
Looks like the cause of this was because the original feature release for PFD did not include code for the PFD value in the parameter set where a VMConfig object is used.

No changes to any customer facing values, only internal business logic of the cmdlet.

Checklist

• I have read the Submitting Changes section of CONTRIBUTING.md
• The title of the PR is clear and informative
• The appropriate ChangeLog.md file(s) has been updated:
  • For any service, the ChangeLog.md file can be found at src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
  • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header -- no new version header should be added
• The PR does not introduce breaking changes
• If applicable, the changes made in the PR have proper test coverage
• For public API changes to cmdlets:
  • a cmdlet design review was approved for the changes in this repository (Microsoft internal only)
    • https://github.com/Azure/azure-powershell-cmdlet-review-pr/issues/new
  • the markdown help files have been regenerated using the commands listed here

[grizzlytheodore]

i'm not sure if I am understanding the title/example correctly. Isnt your code in NewAzureVMCommand.cs adding it for when PlatformFaultDomain is provided from New-AzConfig, not New-AzVmssConfig?

[Sandido]

i'm not sure if I am understanding the title/example correctly. Isnt your code in NewAzureVMCommand.cs adding it for when PlatformFaultDomain is provided from New-AzConfig, not New-AzVmssConfig?

Yes! I edited the title.

[isra-fel]

LGTM