(aws-eks): Allow to only tag selected subnets for load balancer usage

### Describe the feature

In the `Cluster` construct [subnets are tagged](https://github.com/aws/aws-cdk/blob/master/packages/%40aws-cdk/aws-eks/lib/cluster.ts#L1811) so that the AWS load balancer controller can discover them automatically. However, this mechanism automatically tags all private and public subnets.

It should be possible to limit the tagging to the subnets that have been selected through the `SubnetSelection` of the `Cluster`.

### Use Case

We are using certain private subnets only to provide IPs to our EKS clusters' pods. Load balancers should never be placed in those subnets because we don't route into them. With the current tagging mechanism, we need to explicitly specify the subnet IDs for all load balancers in the annotations because all private subnets are tagged.

### Proposed Solution

* Keep the default that all subnets are tagged so that the existing behavior is not broken.
* Add a property of a to be implemented `SubnetTaggingProps` interface to the `ClusterProps` interface -> could look something like this:
```
export interface SubnetTaggingProps {
onlyUseSelectedSubnets: boolean;
tagPrivateSubnets: boolean;
tagPublicSubnets: boolean;
}
```
* Adapt the tagging function in the `Cluster` construct so that it correctly handles the props.

### Other Information

_No response_

### Acknowledgements

- [X] I may be able to implement this feature request
- [ ] This feature might incur a breaking change

### CDK version used

2.20.0

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

Any

Start in packages/@aws-cdk/aws-eks/lib/cluster.ts at the linked Cluster tagging logic, then trace how ClusterProps and SubnetSelection determine the available subnets. Done means adding the proposed controls while preserving the default of tagging all private and public subnets, and limiting tags to selected subnets when requested.

Written by the indexing model from the issue text.