Discrepancy between swagger and service: operationalinsights querypack create operation

The response of service is 201 but swagger definition is 200.

Service response:
```text
PATCH https://management.azure.com/subscriptions/0000000000000000/resourceGroups/resourceGroupName/providers/Microsoft.OperationalInsights/queryPacks/oiquerypacky2c5gX
--------------------------------------------------------------------------------
RESPONSE 201: 201 Created
ERROR CODE UNAVAILABLE
--------------------------------------------------------------------------------
{
"id": "/subscriptions/0000000000000/resourceGroups/resourceGroupName/providers/Microsoft.OperationalInsights/querypacks/oiquerypacky2c5gX",
"name": "oiquerypacky2c5gX",
"properties": {
"queryPackId": "000000000000000",
"timeCreated": "2022-09-22T08:08:05.5075382Z",
"timeModified": "2022-09-22T08:51:56.369753Z",
"provisioningState": "Succeeded"
}
}
```
Swagger: https://github.com/Azure/azure-rest-api-specs/blob/main/specification/operationalinsights/resource-manager/Microsoft.OperationalInsights/stable/2019-09-01/QueryPacks.json#L233

Open specification/operationalinsights/resource-manager/Microsoft.OperationalInsights/stable/2019-09-01/QueryPacks.json around line 233 and inspect the querypack create operation response definition. Compare it with the reported PATCH response, then confirm the Swagger response status matches the service's 201 Created result.

Written by the indexing model from the issue text.