Ignore cert-manager in LBC's webhooks

[rifelpet]

LBC depends on cert-manager but kops can get in a circular dependency loop when applying these manifests on a new cluster.
The cert-manager pods wont be created because the LBC webhook on "CREATE services" isn't working yet, but LBC pod cant be created because it depends on a secret volume mount created by cert-manager

Observe the errors in these protokube logs:

W1218 22:01:20.531717 10658 results.go:63] error from apply on /v1, Kind=Service kube-system/cert-manager: error from apply: error patching object: Internal error occurred: failed calling webhook "mservice.elbv2.k8s.aws": failed to call webhook: Post "https://aws-load-balancer-webhook-service.kube-system.svc:443/mutate-v1-service?timeout=10s": dial tcp 100.69.153.238:443: connect: connection refused

W1218 22:01:22.130490 10658 results.go:63] error from apply on cert-manager.io/v1, Kind=Certificate kube-system/aws-load-balancer-serving-cert: error from apply: error patching object: Internal error occurred: failed calling webhook "webhook.cert-manager.io": failed to call webhook: Post "https://cert-manager-webhook.kube-system.svc:443/mutate?timeout=10s": service "cert-manager-webhook" not found

and kube-system event:

- count: 15
  eventTime: null
  firstTimestamp: "2023-12-18T21:48:54Z"
  involvedObject:
    apiVersion: v1
    kind: Pod
    name: aws-load-balancer-controller-d7cfbcbd4-s42pv
    namespace: kube-system
    resourceVersion: "932"
    uid: ffa0fc59-ed11-42d8-8114-5fc65d33bda4
  lastTimestamp: "2023-12-18T22:03:13Z"
  message: 'MountVolume.SetUp failed for volume "cert" : secret "aws-load-balancer-webhook-tls"
    not found'

This should fix the flakiness in this prow job that started after we upgraded LBC (#16155) that added the "CREATE services" webhook configuration.

[rifelpet]

/test pull-kops-e2e-aws-load-balancer-controller

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hakman

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [hakman]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[hakman]

/test pull-kops-e2e-aws-load-balancer-controller

[hakman]

/lgtm cancel

[rifelpet]

/test pull-kops-e2e-aws-load-balancer-controller

using amd64 nodes for this job because LBC's e2e test uses single-arch images (example)

[rifelpet]

/test pull-kops-e2e-aws-load-balancer-controller

[rifelpet]

/cc @hakman

[hakman]

/lgtm

[jams008]

Hi, i found same issue after enable ALB controller via addos kops. how can fix this issue?
I use kops version client 1.29.0

MountVolume.SetUp failed for volume "cert" : secret "aws-load-balancer-webhook-tls" not found