fix(aws-lb-controller): wait till deployed

[wombelix]

Issue #, if available:

N/A

Description of changes:

AlbController webhook isn't ready directly after the AddOn deployment.
This cause a race condition when another AddOn creates Kubernetes Manifest resources that rely on it, like TargetGroupBinding.
Sometimes it is successful, sometimes not. To avoid such situations, addHelmChart of AlbController should wait similar as it was implemented for External Secrets: #514

Example of such an error when the proposed fix is not applied:

Received response status [FAILED] from custom resource. Message returned: Error: b'Error from server (InternalError): error when creating "/tmp/manifest.yaml": Internal error occurred:
failed calling webhook "mtargetgroupbinding.elbv2.k8s.aws": failed to call webhook: Post "https://aws-load-balancer-webhook-service.kube-system.svc:443/mutate-elbv2-k8s-aws-v1beta1-tar
getgroupbinding?timeout=10s": no endpoints available for service "aws-load-balancer-webhook-service"\n'

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[shapirov103]

LGTM

[shapirov103]

/do-e2e-tests

[aws-ia-ci]

end to end tests failed. A maintainer can provide more details.

[shapirov103]

/do-e2e-tests

[aws-ia-ci]

end to end tests failed. A maintainer can provide more details.

[shapirov103]

validated locally, requires dependency on vpc cni to provide repeatable and reliable results.

Debugged and verified locally