`SiteRecovery@2022-10-01`: `policyId` is returned in different format by `ReplicationProtectionContainerMappings_GET`

GET on [ReplicationProtectionContainerMappings](https://github.com/Azure/azure-rest-api-specs/blob/26e208d700b640667e28221dea6807d853915d69/specification/recoveryservicessiterecovery/resource-manager/Microsoft.RecoveryServices/stable/2022-10-01/service.json#L4605) returns [policyId](https://github.com/Azure/azure-rest-api-specs/blob/26e208d700b640667e28221dea6807d853915d69/specification/recoveryservicessiterecovery/resource-manager/Microsoft.RecoveryServices/stable/2022-10-01/service.json#L19563) in different format.

What I set
```
/subscriptions/{sub1}/resourceGroups/{rg1}/providers/Microsoft.RecoveryServices/vaults/{vault1/replicationPolicies/{policy1}
```

What I get
```
Subscriptions/{sub1}/resourceGroups/{rg1}/providers/Microsoft.RecoveryServices/vaults/{vault1/replicationPolicies/{policy1}
```

Start with the ReplicationProtectionContainerMappings operation and policyId schema in the linked service.json, at the referenced lines. Compare the documented resource ID format with the GET response and check related recovery-services specifications for the expected casing. Done means the API contract and returned policyId format are consistent, with the required correction confirmed by maintainers.

Written by the indexing model from the issue text.