[BUG] [Virtual machine] Error occurred with Arm64-based VMs has little error message returned when trying to assess patches on the VM

Nobody has claimed this yet.

### API Spec link

https://github.com/Azure/azure-rest-api-specs/blob/main/specification/compute/resource-manager/Microsoft.Compute/ComputeRP/stable/2024-07-01/virtualMachine.json#L1827

### API Spec version

2024-07-01

### Describe the bug

Operation VirtualMachines_AssessPatches failed when the VM's architecture is Arm64, and the error message returned by REST API was not enough to describe the issue.
```
{

"startTime": "2024-10-22T06:44:16.3486511+00:00",

"endTime": "2024-10-22T06:44:34.6455815+00:00",

"status": "Failed",

"error": {

"code": "VMGuestPatchInternalError",

"message": "An internal execution error occurred. Please retry later."

},

"name": "xxxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"

}
```

Yet from kusto query, we can get more detailed exception message:

### Expected behavior

We can get more detailed exception message from REST API like it shows in the kusto.

### Actual behavior

REST API only returns message: `An internal execution error occurred. Please retry later`.

### Reproduction Steps

1. Create an Arm64-based VM resource.
2. Call API: https://learn.microsoft.com/en-us/rest/api/compute/virtual-machines/assess-patches?view=rest-compute-2024-07-01&tabs=HTTP

### Environment

_No response_

Start with the 2024-07-01 Compute virtualMachine.json definition and the VirtualMachines_AssessPatches operation linked in the issue. Reproduce the request against an Arm64-based VM, compare the REST error with the detailed Kusto exception, and trace whether the specification or another referenced entry point defines the returned message. Done means the REST API exposes a sufficiently detailed error for this failure.

Written by the indexing model from the issue text.