opensearch create-vpc-endpoint no longer returns VpcEndpoint .Endpoint

### Describe the bug

The struct returned by `create-vpc-endpoint` no longer includes `Endpoint` (see [docs](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/opensearch/create-vpc-endpoint.html)) which is blocking resource creation for my team because we use a CDK `AwsCustomResource` to wrap this call.

### Expected Behavior

The `Endpoint` field should exist in the response
```
{
"VpcEndpoint": {
"VpcEndpointId": "...",
"VpcEndpointOwner": "...",
"DomainArn": "...",
"VpcOptions": {
"VPCId": "...",
"SubnetIds": [
"...",
],
"AvailabilityZones": [
"us-east-1b",
"us-east-1a",
"us-east-1c"
],
"SecurityGroupIds": [
"..."
]
},
"Status": "CREATING",
"Endpoint": "....."
}
}
```

### Current Behavior

The `Endpoint` field does not exist in the response

```
{
"VpcEndpoint": {
"VpcEndpointId": "...",
"VpcEndpointOwner": "...",
"DomainArn": "...",
"VpcOptions": {
"VPCId": "...",
"SubnetIds": [
"...",
],
"AvailabilityZones": [
"us-east-1b",
"us-east-1a",
"us-east-1c"
],
"SecurityGroupIds": [
"..."
]
},
"Status": "CREATING",
}
}
```

Example from attempting to deploy the CDK custom resource:
```
CustomResource attribute error: Vendor response doesn't contain VpcEndpoint.Endpoint attribute in object
```

### Reproduction Steps

```
aws opensearch create-vpc-endpoint --domain-arn --vpc-options SubnetIds=subnet-1,subnet-2,subnet-,SecurityGroupIds=sg-1
```

### Possible Solution

_No response_

### Additional Information/Context

This behavior changed sometime since 2024-07-30 because the command worked as expected at that time.

### CLI version used

2.17.10

### Environment details (OS name and version, etc.)

Linux/5.10