missing ENABLE_IPv4 and ENABLE_IPv6 variable for cni version 1.10

[ismailyenigul]

Describe the bug
aws cni 1.10.X has two new variables

ENABLE_IPv4=true
ENABLE_IPv6=false

Upgrading my 1.9.x manifests to run a 1.10.x container image get SIGSEGV because of missing above two variables

Defaulted container "aws-node" out of: aws-node, aws-vpc-cni-init (init)
{"level":"info","ts":"2022-08-19T07:51:24.172Z","caller":"entrypoint.sh","msg":"Validating env variables ..."}
{"level":"info","ts":"2022-08-19T07:51:24.173Z","caller":"entrypoint.sh","msg":"Install CNI binaries.."}
{"level":"info","ts":"2022-08-19T07:51:24.185Z","caller":"entrypoint.sh","msg":"Starting IPAM daemon in the background ... "}
{"level":"info","ts":"2022-08-19T07:51:24.188Z","caller":"entrypoint.sh","msg":"Checking for IPAM connectivity ... "}
{"level":"info","ts":"2022-08-19T07:51:26.195Z","caller":"entrypoint.sh","msg":"Retrying waiting for IPAM-D"}
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x39 pc=0x5564aa055418]

goroutine 422 [running]:
github.com/aws/amazon-vpc-cni-k8s/pkg/ipamd.(*IPAMContext).StartNodeIPPoolManager(0xc00022c768)
	/go/src/github.com/aws/amazon-vpc-cni-k8s/pkg/ipamd/ipamd.go:640 +0x18
created by main._main
	/go/src/github.com/aws/amazon-vpc-cni-k8s/cmd/aws-k8s-agent/main.go:64 +0x2bb
{"level":"info","ts":"2022-08-19T07:51:28.200Z","caller":"entrypoint.sh","msg":"Retrying waiting for IPAM-D"}
{"level":"info","ts":"2022-08-19T07:51:30.206Z","caller":"entrypoint.sh","msg":"Retrying waiting for IPAM-D"}

To Reproduce
run kubergrunt eks sync-core-components on EKS 1.21
see aws/amazon-vpc-cni-k8s#1854

// paste code snippets here

Expected behavior
Better to patch aws-node daemonset with above new envs or add a notes to release notes or kubergrunt for required change

Nice to have

• Terminal output
• Screenshots

Additional context
Add any other context about the problem here.