[Compute] AZ and VMSS rolling upgrade update and tests

[hyonholee]

Azure/azure-rest-api-specs#1727

Description

---

This checklist is used to make sure that common guidelines for a pull request are followed.

• I have read the contribution guidelines.
• The pull request does not introduce breaking changes.

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.

Testing Guidelines

• Pull request includes test coverage for the included changes.

SDK Generation Guidelines

• If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
• The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code.
• The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK.

[markcowl]

Also, can you update the generate.cmd and include the metadata file that is generated when you runit?

[markcowl]

Why is this in the repo?

[shahabhijeet]

Provide a clear description that describes the reason for the PR. Explain the change in detail.
Failing to do this, will result in PR not being reviewed.
This is a public repo and every PR should be clearly explained as to what the PR is all about.

[shahabhijeet]

@hyonholee pleaes reopen the same PR once you have addressed all feedback/questions.
Having a PR open for more than a week affects our SLA data.