[BUG] PUT operation for privateendpoint connection approval is not idempotent

### API Spec link

https://learn.microsoft.com/en-us/rest/api/storagerp/private-endpoint-connections/put?view=rest-storagerp-2023-05-01&tabs=HTTP

### API Spec version

2023-05-01

### Describe the bug

Trying to approve the private endpoint connection , which is in Approved state shouldnt throw error for idempotent operations.
But getting

```
│ {
│ "error": {
│ "code": "InvalidValuesForRequestParameters",
│ "message": "Values for request parameters are invalid: privateLinkServiceConnectionState.status."
│ }

```

### Expected behavior

Api can be hit any number of times for PUT operation

### Actual behavior

```
│ {
│ "error": {
│ "code": "InvalidValuesForRequestParameters",
│ "message": "Values for request parameters are invalid: privateLinkServiceConnectionState.status."
│ }

```

### Reproduction Steps

1) Create a manual approval private endpoint
2) Use https://learn.microsoft.com/en-us/rest/api/storagerp/private-endpoint-connections/put?view=rest-storagerp-2023-05-01&tabs=HTTP to approve private endpoint
3) Run step2 again , it shouldn't throw error. but it giving error

### Environment

_No response_

Start with the linked Microsoft REST API specification for the private-endpoint-connections PUT operation, using API version 2023-05-01. Reproduce the approval request from the listed steps, then repeat it for an already Approved connection and compare the response with the expected idempotent behavior. Done means repeated approval requests no longer return the InvalidValuesForRequestParameters error.

Written by the indexing model from the issue text.