Fix P0/P1 LRO response-mismatch violations (lro-response-mismatch rule)

The new linter rule [`@azure-tools/typespec-azure-resource-manager/lro-response-mismatch`](https://github.com/Azure/typespec-azure/pull/4145) flagged ARM long-running operations whose encoded `finalResult` does not match the operation shape's required result. See the full [**LRO Response Mismatch Rule Evaluation**](https://github.com/markcowl/azure-rest-api-specs/blob/eval-typespec-next/lro-rule-eval.md) for methodology, per-violation evidence, and recommended fixes.

This issue tracks fixing the **Priority 0** and **Priority 1** services (those with recommended source fixes and a recent latest API version). Check off each spec as it is fixed.

### Priority 0

- [ ] **`Microsoft.AzureResilienceManagement`** — 28 violations (21 recommended fixes) — [`specification/azureresiliencemanagement/resource-manager/Microsoft.AzureResilienceManagement/AzureResilienceManagement`](https://github.com/Azure/azure-rest-api-specs/blob/typespec-next/specification/azureresiliencemanagement/resource-manager/Microsoft.AzureResilienceManagement/AzureResilienceManagement)
- [ ] **`Microsoft.Cdn`** — 6 violations (5 recommended fixes) — [`specification/cdn/resource-manager/Microsoft.Cdn/Cdn`](https://github.com/Azure/azure-rest-api-specs/blob/typespec-next/specification/cdn/resource-manager/Microsoft.Cdn/Cdn)
- [ ] **`Microsoft.DeviceRegistry`** — 3 violations (3 recommended fixes) — [`specification/deviceregistry/DeviceRegistry.Management`](https://github.com/Azure/azure-rest-api-specs/blob/typespec-next/specification/deviceregistry/DeviceRegistry.Management)
- [ ] **`Microsoft.RecoveryServices`** — 1 violation (1 recommended fix) — [`specification/recoveryservices/resource-manager/Microsoft.RecoveryServices/RecoveryServices`](https://github.com/Azure/azure-rest-api-specs/blob/typespec-next/specification/recoveryservices/resource-manager/Microsoft.RecoveryServices/RecoveryServices)

### Priority 1

- [ ] **`Microsoft.ApiManagement`** — 2 violations (1 recommended fix) — [`specification/apimanagement/resource-manager/Microsoft.ApiManagement/ApiManagement`](https://github.com/Azure/azure-rest-api-specs/blob/typespec-next/specification/apimanagement/resource-manager/Microsoft.ApiManagement/ApiManagement)
- [ ] **`Microsoft.AzureDataTransfer`** — 15 violations (3 recommended fixes) — [`specification/azuredatatransfer/AzureDataTransfer.Management`](https://github.com/Azure/azure-rest-api-specs/blob/typespec-next/specification/azuredatatransfer/AzureDataTransfer.Management)

Read the LRO Response Mismatch Rule Evaluation first, then inspect the linked TypeSpec sources under the six listed service paths. Start with the P0 services and compare each violation with its recommended source fix. Done means the recommended P0 and P1 fixes are applied and every listed service is checked off without the reported response-mismatch violations.

Written by the indexing model from the issue text.