(aws-eks-v2-alpha): (tags not propagating to the construct custom resources and being blocked)

### Describe the feature

Custom resources created by the Cluster construct and other constructs need to inherit the tags of the cluster and stack if they are supplied.

### Use Case

We have tag enforcement SCPs for Lambda and few other critical services. The Lambdas for the custom resources, such as OpenID Connect Provider and CFN Utils Provider are being blocked from being created because they do not have any tags so the deployment is failing when you use the property for alb_controller.

### Proposed Solution

All custom resource providers (Lambdas) should inherit the tags of the construct that is being created.

### Other Information

Here is a gist with the code to reproduce the situation: [eks_stack](https://gist.github.com/tomburge/a2bf879b2939d7a13349adf87c57ae2d)

The only way to workaround currently is install the alb controller separately.

### Acknowledgements

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

### AWS CDK Library version (aws-cdk-lib)

2.212.0a0

### AWS CDK CLI version

2.1026.0

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

Windows 11

Start with the Cluster construct and the custom resource providers used by the alb_controller property. Use the linked eks_stack gist to reproduce the blocked Lambda deployment, then trace how cluster and stack tags reach those providers. Done means the custom resource Lambdas inherit supplied tags and the reproduction deploys under the stated tag-enforcement SCPs.

Written by the indexing model from the issue text.