PrivateDNS support for VPCEndpointService construct

[tsykora-verimatrix]

VPCEndpointService construct works well but it lacks PrivateDNS support so service consumers need to use the long generated DNS name which can change when redeploying the endpoint service. AWS supports PrivateDNS functionality for custom endpoint services.
Would it be possible to add PrivateDNS (with DNS validation) support to VPCEndpointService construct?

Use Case

Service consumers can consume endpoint service via friendly private DNS name instead of generated DNS name that can change (which impacts any application that is using it).

Proposed Solution

add support for PrivateDNS with validation to VPCEndpointService construct.

Other

• 👋 I may be able to implement this feature request
• ⚠️ This feature might incur a breaking change

---

This is a 🚀 Feature Request

[MrArnoldPalmer]

Looks like this was completed via #10780.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.