Feature request to allow additional VPC's added to private networking of EKS API server.

Current behaviour:

When private and public is enabled:
- The VPC where EKS is hosted will resolve to private IP's and every other VPC/network will resolve public IP's.

Requested behaviour:
- Allow to add additional VPC's to the resolve private IP's of the cluster.
Usecase :
- Assuming the architecture has Peering connections or Transit gateway's to connect in-between VPC's in such scenarios it will help to have private resolution of the domain and communicate via private networking.

Available solutions at the moment:
- Use Route 53 resolver.
- Use custom DNS resolver on the host machine.

Start by reviewing the requested private DNS behavior for EKS API servers and the listed peering or Transit Gateway use case, then compare the existing Route 53 Resolver and custom DNS approaches. Done means additional VPCs resolve the cluster domain to private IPs and communicate through private networking.

Written by the indexing model from the issue text.