[Query] RecoveryServicesBackup - ProtectionContainers DELETE operation is async but missing LRO property in the swagger

### API Spec link

https://github.com/Azure/azure-rest-api-specs/blob/main/specification/recoveryservicesbackup/resource-manager/Microsoft.RecoveryServices/stable/2025-02-01/bms.json#L3180-L3240

### API Spec version

2025-02-01, 2025-08-01

### Question/Query

The DELETE operation for ProtectionContainers is asynchronous. But it misses LRO property in the swagger. Downstream services thus have to manually parse and poll results. Could you please help add LRO property into this operation? Similar issue https://github.com/Azure/azure-rest-api-specs/issues/22758, PR for RecoveryServicesBackup - ProtectedItems: https://github.com/Azure/azure-rest-api-specs/pull/23524,

```
DELETE https://management.azure.com/subscriptions/xxx/resourceGroups/ase-tfm-test-rg/providers/Microsoft.RecoveryServices/vaults/ase-tfm-test-rsv/backupFabrics/Azure/protectionContainers/VMAppContainer;Compute;ase-tfm-test-rg;ase-tfm-test-vm?api-version=2025-02-01 HTTP/2.0

x-ms-correlation-request-id: f57f1dc3-a237-4a02-8c17-28b197fb20d7

Status Code: 202
content-type: application/json; charset=utf-8

```

### Environment

_No response_

Open specification/recoveryservicesbackup/resource-manager/Microsoft.RecoveryServices/stable/2025-02-01/bms.json around lines 3180-3240 and inspect the ProtectionContainers DELETE operation. Compare it with the cited issue 22758 and ProtectedItems PR 23524 to understand the expected LRO representation. Done means the asynchronous 2025-02-01 and 2025-08-01 operations expose the needed LRO property in the API specification.

Written by the indexing model from the issue text.