feat: Add support for dns_options on VPC endpoints

[erezo9]

Description

add dns_options block to use it in cases of endpoints that support gateway and interface

Motivation and Context

• Resolves Cannot create S3 VPC Endpoint with private DNS enabled. #982

Breaking Changes

How Has This Been Tested?

• I have updated at least one of the examples/* to demonstrate and validate my change(s)
• I have tested and validated these changes using one or more of the provided examples/* projects

there is no user input change, if the array is not existend or private_dns_enabled is false it will not trigger a change

tested locally

• I have executed pre-commit run -a on my pull request

[erezo9]

@antonbabenko if you could please review this or tag relavent people to review
will be super helpful if this be in the next version

[zach-nicoll-wcq]

Would love to see this merged!! Currently blocking a private MWAA deployment because Terraform doesn't support this.

[erezo9]

@bryantbiggs
Can you please review this MR, i cant assign reviewers to view this code and it will really help in the provisioning

[antonbabenko]

This PR is included in version 5.5.0 🎉

[erezo9]

@bryantbiggs thanks for merging
why did you change the looping validation and the check on the private_dns_enabled?
i added it so it could prevent users from using this when its type gateway and when private_dns_enabled = true the value should not exist

[bryantbiggs]

the value should not exist

Then users should not provide it. Sometimes we can provide the means to help users avoid misconfiguration, but in this scenario the logic would be overly complex

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.