[Azure Search] Replacing generate.cmd with generate.ps1 and regenerat…

[brjohnstmsft]

…ing all code

Description

Per prior PR feedback from @dsgouda, we are replacing generate.cmd with generate.ps1 everywhere. I re-generated all code to test that the new scripts work, and they do. None of the code changed since none of the specs changed in the past few days.

Please note that this PR is targeting a branch that is owned by the Azure Search team.

FYI @natinimni @chaosrealm @mhko @shahabhijeet

---

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

• Please add REST spec PR link to the SDK PR
• 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.

[mhko]

LGTM

[dsgouda]

LGTM