[Compute] Add Gallery scripts specs

[viveklingaiah]

• Add Gallery Script, Gallery Script Version APIs
• Gallery Scripts helps store user's commonly used scripts in gallery and make them shareable, reusable.
  API design doc: https://microsoft.sharepoint.com/:w:/t/ComputeVM/ER0OOJwCfPtCtOp_0yrkXmQBmniHv1liTdsHSJGtFDQCWw?e=r1a539

===

Choose a PR Template

Switch to "Preview" on this description then select one of the choices below.

Click here to open a PR for a Control Plane (ARM) API.

[openapi-pipeline-app]

Next Steps to Merge

✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge.

[openapi-pipeline-app]

PR validation pipeline restarted successfully. If there is ApiView generated, it will be updated in this comment.

[ramoka178]

@viveklingaiah Please fix the Swagger Avocado and Swagger Lintdiff errors and place it back in queue for review.

[gary-x-li]

Can you please address the two latest comments regarding headers for PUT?

[viveklingaiah]

Can you please address the two latest comments regarding headers for PUT?

Yes, addressed.

[gary-x-li]

The description of the Location header you added is "Geo-location (region) of the resource". This is not correct. Please make sure you go through the RPC for async operations below; and make sure your service behaves the same way as how this is defined in swagger.

https://github.com/cloud-and-ai-microsoft/resource-provider-contract/blob/master/v1.0/async-api-reference.md#creating-replacing-or-updating-resources-asynchronously

In particular, if you are following the async 200/201 PUT pattern, the Location header is not relevant (since it's for the 202 Accepted pattern). The Azure-AsyncOperation header is optional. You should make sure the swagger definition is consistent with what your service would respond.

[viveklingaiah]

The description of the Location header you added is "Geo-location (region) of the resource". This is not correct. Please make sure you go through the RPC for async operations below; and make sure your service behaves the same way as how this is defined in swagger.

https://github.com/cloud-and-ai-microsoft/resource-provider-contract/blob/master/v1.0/async-api-reference.md#creating-replacing-or-updating-resources-asynchronously

In particular, if you are following the async 200/201 PUT pattern, the Location header is not relevant (since it's for the 202 Accepted pattern). The Azure-AsyncOperation header is optional. You should make sure the swagger definition is consistent with what your service would respond.

I think addressed this time. Please check

[grizzlytheodore]

migrated to PR parallel for TypeSpec change
#35887