VPC-CNI minimal image builds

[jdn5126]

What type of PR is this?
Enhancement

Which issue does this PR fix:
N/A

What does this PR do / Why do we need it:
This pull request migrates the VPC-CNI and VPC-CNI init images to use EKS minimal build image. This PR applied the diff from #1726 and updated it to handle recent changes. It was also tested to be compatible with #2137 , but those changes were left commented out as #2137 is not yet complete.

The VPC CNI image is based on public.ecr.aws/eks-distro-build-tooling/eks-distro-minimal-base-iptables:latest.2, which installs iptables-legacy and iptables-nft, but sets iptables-legacy as the default using update-alternatives.

The VPC CNI init image is based on public.ecr.aws/eks-distro-build-tooling/eks-distro-minimal-base-glibc:latest.2. The reason I could not use the base image is that the binaries are built in pie mode for security reasons, and building with pie requires the loader to be loaded despite the binary being static.

I considered splitting this into two PRs: one to add the Golang entrypoints and one to do the move, but concluded that it is easiest to do as one PR, and if there are any issues, it is simple to just revert the move.

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

Testing done on this change:
I manually verified that all integration tests pass against this change. Output for init container:

$ kubectl logs aws-node-rg6rm -n kube-system -c aws-vpc-cni-init
time="2022-11-21T19:35:43Z" level=info msg="Copying CNI plugin binaries ..."
time="2022-11-21T19:35:43Z" level=info msg="Copied all CNI plugin binaries to /host/opt/cni/bin\n"
Installed /host/opt/cni/bin/loopback
Installed /host/opt/cni/bin/portmap
Installed /host/opt/cni/bin/bandwidth
Installed /host/opt/cni/bin/aws-cni-support.sh
time="2022-11-21T19:35:43Z" level=info msg="Found primaryMAC 0a:55:51:01:a4:d1"
time="2022-11-21T19:35:43Z" level=info msg="Found primaryIF eth0"
time="2022-11-21T19:35:43Z" level=info msg="Updated net/ipv4/conf/eth0/rp_filter to 2"
time="2022-11-21T19:35:43Z" level=info msg="Updated net/ipv4/tcp_early_demux to 1"
time="2022-11-21T19:35:43Z" level=info msg="CNI init container done"

Output for VPC-CNI:

$ kubectl logs aws-node-rg6rm -n kube-system -c aws-node
time="2022-11-21T19:35:43Z" level=info msg="Install CNI binaries.."
Installed /host/opt/cni/bin/aws-cni
time="2022-11-21T19:35:43Z" level=info msg="Starting IPAM daemon... "
time="2022-11-21T19:35:43Z" level=info msg="Checking for IPAM connectivity... "
Installed /host/opt/cni/bin/egress-v4-cni
time="2022-11-21T19:35:44Z" level=info msg="Copying config file... "
time="2022-11-21T19:35:44Z" level=info msg="Successfully copied CNI plugin binary and config file."

Automation added to e2e:
N/A

Will this PR introduce any new dependencies?:
No, it will actually reduce dependencies.

Will this break upgrades or downgrades. Has updating a running cluster been tested?:
This will not break upgrades or downgrades. Upgrade and downgrade has been tested with a running cluster.

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

Does this PR introduce any user-facing change?:
The image base is different.

Move VPC CNI and VPC CNI init images to use EKS minimal base image.

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

[bwagner5]

Nice! Do you know the full image size differences?

[jdn5126]

Nice! Do you know the full image size differences?

Comparing upstream (v1.12.0) to my personal ECR:
VPC-CNI Init: 277.24 MB -> 19.90MB
VPC-CNI: 293.37 MB -> 47.67MB

[bryantbiggs]

awesome work @jdn5126 🎉