adding feature flags to configmap charts

[haouc]

What type of PR is this?

Which issue does this PR fix:
This PR is adding support for new feature flags into helm charts

What does this PR do / Why do we need it:
We have enabled supported for multiple new features but the flags are still missing in helm.

If an issue # is not available please add repro steps and logs from IPAMD/CNI showing the issue:

Testing done on this change:

Installed the charts locally

% kk get cm amazon-vpc-cni -oyaml
apiVersion: v1
data:
  branch-eni-cooldown: "60"
  enable-network-policy-controller: "false"
  enable-windows-ipam: "false"
  enable-windows-prefix-delegation: "false"
  minimum-ip-target: "0"
  warm-ip-target: "0"
  warm-prefix-target: "0"
kind: ConfigMap
metadata:
  annotations:
    meta.helm.sh/release-name: aws-vpc-cni
    meta.helm.sh/release-namespace: kube-system
  creationTimestamp: "2023-12-18T20:37:12Z"
  labels:
    app.kubernetes.io/instance: aws-vpc-cni
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: aws-node
    app.kubernetes.io/version: v1.15.4
    helm.sh/chart: aws-vpc-cni-1.15.4
    k8s-app: aws-node
  name: amazon-vpc-cni
  namespace: kube-system
  resourceVersion: "1345600"
  uid: 1050d013-5ee9-4810-9e7c-2077645f1eea

Tested change default value:
Changed the cooldown window to 90s

apiVersion: v1
data:
  branch-eni-cooldown: "90"
  enable-network-policy-controller: "false"
  enable-windows-ipam: "false"
  enable-windows-prefix-delegation: "false"
  minimum-ip-target: "0"
  warm-ip-target: "0"
  warm-prefix-target: "0"
kind: ConfigMap

Will this PR introduce any new dependencies?:

no
Will this break upgrades or downgrades? Has updating a running cluster been tested?:
no

Does this change require updates to the CNI daemonset config files to work?:

no
Does this PR introduce any user-facing change?:

yes

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.