Generate cmdlets from forked AutoREST.PowerShell repository.

[timayabi2020]

Fixes #1570 and #2476

Changes proposed in this pull request

• Adds forked Autorest as a submodule which will be used to generate cmdlets.
• Updates custom commands in the group module to include custom header parameter as expected by the auto generated Client API class.
• Updates pipelines to run generation using the forked AutoREST.PowerShell repo.
• Updates the global directive file (readme.graph.md) to point to the AutoREST.PowerShell submodule.

Generated cmdlets were published to an internal feed. Using cmdlets obtained from that feed manual tests involving PATCH, POST and DELETE operations were done while raptor handled GET operations. Use this script to register the feed as a PS repository.

Sample cmdlet with optional custom header parameter

**Sample cmdlet extracting the correct media type from file inputs and setting the correct request content type. (Intitally all input file requests defaulted to application/octet-stream

Sample cmdlet with optional parameter for specifying the media/content type for file inputs

Sample raptor test run results for stable tests
NB This was locally run because the feed was registered locally.

[calebkiage]

Is it possible to use the same syntax as CLI for headers?

i.e. --headers AcceptLanguage=en

[sebastienlevert]

I agree that the semicolon is a weird character for this situation. I'd rather have an actual hashtable / PSObject. Easier to build dynamically if needs be.

Thoughts?

[timayabi2020]

@calebkiage @sebastienlevert yes it can change, however I preferred the approach of setting http headers the way it is normally done in a curl request. e.g curl -H "Content-Type: application/json" https://graph.com.........

[sebastienlevert]

I think we should be using the same approach that Invoke-WebRequest (and other similar Cmdlets) are using. https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.utility/invoke-webrequest?view=powershell-7.4#-headers

[peombwa]

Thanks for addressing on the most asked for feature! Please see my comment below on improvements to the UX of the parameter.

[peombwa]