[AWS::OpenSearchService::Domain] - [BUG] - CloudControl UpdateResource fails with unrecognized advanced option 'override_main_response_version'

### Name of the resource

AWS::OpenSearchService::Domain

### Resource Name

_No response_

### Issue Description

Using CloudControl for AWS::OpenSearchService::Domain, UpdateResource fails with:

Invalid request provided: Unrecognized advanced option 'override_main_response_version' passed in advancedOptions.

The caller does not set advancedOptions.override_main_response_version.
This appears to be a CloudControl/OpenSearch model drift issue where an AWS-managed/internal advanced option is replayed during update and then rejected by OpenSearch validation.

### Expected Behavior

UpdateResource should succeed for unrelated changes (for example EBSOptions.VolumeSize) when unsupported AdvancedOptions keys are not provided by the caller.

### Observed Behavior

UpdateResource fails with InvalidRequest and the unrecognized advanced option error, even though that key is absent from caller inputs.

### Test Cases

1. Create AWS::OpenSearchService::Domain (for example EngineVersion=OpenSearch_3.1, InstanceType=t3.small.search, EBSOptions.VolumeSize=10).
2. Confirm create succeeds.
3. Call UpdateResource with only EBSOptions.VolumeSize changed (10 -> 11).
4. Observe failure: Unrecognized advanced option 'override_main_response_version' passed in advancedOptions.

### Other Details

Other Details

- External reproduction report: https://github.com/pulumi/pulumi-aws-native/issues/2841
- Similar historical OpenSearch/coverage-roadmap issues:
- https://github.com/aws-cloudformation/cloudformation-coverage-roadmap/issues/1496
- https://github.com/aws-cloudformation/cloudformation-coverage-roadmap/issues/1288

Start with the AWS::OpenSearchService::Domain CloudControl UpdateResource path and compare the resource model's advancedOptions handling with the reported OpenSearch validation error. Reproduce the change from EBSOptions.VolumeSize 10 to 11, then verify that an unsupported override_main_response_version value is no longer replayed during unrelated updates; consult the linked Pulumi and coverage-roadmap reports for context.

Written by the indexing model from the issue text.