adding Invoke-AzVmAssessPatch cmdlet.

[grizzlytheodore]

Description

adding Invoke-AzVmAssessPatch cmdlet.

And also updated computecommontest to not have space in the location return for Get-ComputeVmLocation
and added a function that will return an available sku for given subscription, location, and resourcetype.

Design: https://github.com/Azure/azure-powershell-cmdlet-review-pr/issues/634

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)
  • the markdown help files have been regenerated using the commands listed here

[adxsdkps]

Can one of the admins verify this patch?

[isra-fel]

Hey @grizzlytheodore , I know this PR has passes design review, but the name Invoke-AzVmAssessPatch might be a little bit misleading. Putting the word "Patch" at the end makes it sound like invoking a patch to me, however what the command actually does it to invoke an assessment, right?

So I suggest Invoke-AzVmPatchAssess or Invoke-AzVmPatchAssessment. To be frank, Get-AzVmPatch could be even better because it describes the nature of the function accurately and simply.

Let me know what you think. Thanks.

cc @VeryEarly

[grizzlytheodore]

moved to #12658