Feature/cni custom network

[qtruong77]

What does this PR do?

Enable provision EKS cluster with secondary CIDR with CNI custom networking.

Motivation

This feature will be a high demand where we don't want to consume primary CIDR range for EKS environment with enterprise environment

More

• Yes, I have tested the PR using my local account setup (Provide any test evidence report under Additional Notes)
• Yes, I have added a new example under examples to support my PR
• Yes, I have created another PR for add-ons under add-ons repo (if applicable)
• Yes, I have updated the docs for this feature
• Yes, I ran pre-commit run -a with this PR

Note: Not all the PRs required examples and docs except a new pattern or add-on added.

For Moderators

• E2E Test successfully complete before merge?

Additional Notes

An initial PR to have the team review on the changes.
The implementation is based on this tutorial:

• Create an optional step to configure custom network right after the control plan is up with auth configmap (this step is enable by provide input pod_subnet_ids
• Use null_resource to update the daemonset environment variable and apply the manifest due to limitation of the kubernetes_daemonset and kubernetes_manifest resource of kubernetes provider
• Update the max_pod value for worker node

[askulkarni2]

This was done in #778