MarketplaceOrdering SDK update

[alkigel]

All SDK Contribution checklist:

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

• Please open PR in Draft mode if it is:
  • Work in progress or not intended to be merged.
  • Encountering multiple pipeline failures and working on fixes.
• 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.
• I have read the contribution guidelines.
• The pull request does not introduce breaking changes.

General Guidelines and Best Practices

• 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

• 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. (Track 2 only)
• The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK. Please double check nuget.org current release version.

Additional management plane SDK specific contribution checklist:

Note: Only applies to Microsoft.Azure.Management.[RP] or Azure.ResourceManager.[RP]

• Include updated management metadata.
• Update AzureRP.props to add/remove version info to maintain up to date API versions.

Management plane SDK Troubleshooting

• If this is very first SDK for a services and you are adding new service folders directly under /SDK, please add new service label and/or contact assigned reviewer.
• If the check fails at the Verify Code Generation step, please ensure:
  • Do not modify any code in generated folders.
  • Do not selectively include/remove generated files in the PR.
  • Do use generate.ps1/cmd to generate this PR instead of calling autorest directly.
    Please pay attention to the @microsoft.csharp version output after running generate.ps1. If it is lower than current released version (2.3.82), please run it again as it should pull down the latest version,

Old outstanding PR cleanup

Please note:
If PRs (including draft) has been out for more than 60 days and there are no responses from our query or followups, they will be closed to maintain a concise list for our reviewers.

[m-nash]

Is this PR still being worked on? If it is a work in progress can you convert it to a draft PR?

[m-nash]

Please provide the spec pr link associated with this change

[m-nash]

This will result in a breaking change, please provide the corresponding spec PR. The spec PR either needs the approved-breakingchange label from the breaking change team OR we will need to find another way to do this. One option is if ErrorResponseException inherits from CloudException

[alkigel]

the PR link: Azure/azure-rest-api-specs#12469
This is indeed a PR with breaking changes, a new version of the swagger was introduced in the PR because of this.
Can you advise on how to get an approval for this from the breaking change team?

[m-nash]

On the spec PR it has a link which should get you to the right place. I have added it here for your convenience http://aka.ms/bcforapi

[markcowl]

/azp run net - mgmt - ci

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[allenjzhang]

This PR has been outstanding for quite a while. Please reopen if additional info is provided. Thx