Microsoft.OperationalInsights/workspaces/savedSearches resource contains `etag` property defined in the wrong place

Reported in this comment: https://github.com/Azure/bicep/issues/784#issuecomment-923971156

Microsoft.OperationalInsights/workspaces/savedSearches has the "etag" property defined as a top-level resource property:
```json
{
"name": "mySearch",
"type": "Microsoft.OperationalInsights/workspaces/savedSearches",
"etag": "*",
"properties": {
}
}
```

It appears this in fact should be declared inside the "properties" body of this resource type:
```json
{
"name": "mySearch",
"type": "Microsoft.OperationalInsights/workspaces/savedSearches",
"properties": {
"etag": "*"
}
}
```

Here's where this is declared in the RP swagger:

https://github.com/Azure/azure-rest-api-specs/blob/88e7838a09868a51de3894114355c75929847a46/specification/operationalinsights/resource-manager/Microsoft.OperationalInsights/stable/2020-08-01/SavedSearches.json#L267-L270

Start with specification/operationalinsights/resource-manager/Microsoft.OperationalInsights/stable/2020-08-01/SavedSearches.json around lines 267-270 and compare the etag declaration with the issue's examples. Move the declaration to the location indicated by the RP swagger, then run the repository's applicable specification validation; done means the resource schema places etag under properties.

Written by the indexing model from the issue text.