Upgrade to beta apis

[ytsarev]

Description of your changes

Migrate to beta karpenter APIs

• Migrate to latest version and beta APIs
• make configuration installation more reliable
• Update policy to comply with new karpenter version
• Add make e2e SKIP_DELETE=--skip-delete ability to Makefile for debugging setup
• Consume latest https://github.com/upbound/configuration-aws-eks-irsa/releases/tag/v0.4.1 with the ConfigMap deletion policy fix

I have:

• Read and followed Upbound's contribution process.
• Run make reviewable to ensure this PR is ready for review.
• Added backport release-x.y labels to auto-backport this PR, as appropriate.

How has this code been tested

k apply -f test/workload.yaml
k get nodeclaims.karpenter.sh
NAME            TYPE         ZONE         NODE                                            READY   AGE
default-6dvqb   c6g.xlarge   us-west-2b   ip-192-168-117-198.us-west-2.compute.internal   True    26m
 k get pod
NAME                        READY   STATUS    RESTARTS   AGE
workload-7bf7b77746-f4qjs   1/1     Running   0          41m
workload-7bf7b77746-g228r   1/1     Running   0          41m
workload-7bf7b77746-k9ckp   1/1     Running   0          41m
workload-7bf7b77746-n8zv6   1/1     Running   0          41m
workload-7bf7b77746-ss8c5   1/1     Running   0          41m

[ytsarev]

@haarchri we can also offload InstanceProfile creation to the karpenter now and rely on NodeCLass.spec.role if needed but I would leave it to additional PR

As in https://aws.amazon.com/blogs/containers/karpenter-graduates-to-beta/

The Karpenter spec.instanceProfile field has been removed from the EC2NodeClass in favor of the spec.role field. Karpenter now auto-generates the instance profile in your EC2NodeClass given the role that you specify.

In fact instanceProfile is not fully deprecated by the new capability if its management by karpenter is there

[ytsarev]

/test-examples

[ytsarev]

/test-examples