Disable tolerateAllTaints on kOps

[torredil]

CI is failing due to the node pod on the control plane node being stuck in a CrashLoopBackOff state. This PR prevents the node pod from being scheduled on the control plane node.

See logs:

## Printing pod ebs-csi-node-x4nn2 ebs-plugin container logs
#
I1020 18:45:18.555825       1 driver.go:77] "Driver Information" Driver="ebs.csi.aws.com" Version="v1.24.0"
I1020 18:45:18.555934       1 node.go:82] "[Debug] Retrieving node info from metadata service"
I1020 18:45:18.555942       1 node.go:84] "regionFromSession Node service" region=""
I1020 18:45:18.555953       1 metadata.go:85] "retrieving instance data from ec2 metadata"
I1020 18:45:21.697673       1 metadata.go:88] "ec2 metadata is not available"
I1020 18:45:21.697695       1 metadata.go:96] "retrieving instance data from kubernetes api"
I1020 18:45:21.698336       1 metadata.go:101] "kubernetes api is available"
panic: error getting Node i-03843a6ba2de8e36b: Get "[https://100.64.0.1:443/api/v1/nodes/i-03843a6ba2de8e36b](https://100.64.0.1/api/v1/nodes/i-03843a6ba2de8e36b)": dial tcp 100.64.0.1:443: i/o timeout

goroutine 1 [running]:
github.com/kubernetes-sigs/aws-ebs-csi-driver/pkg/driver.newNodeService(0xc000094d20)
	/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/pkg/driver/node.go:87 +0x3e5
github.com/kubernetes-sigs/aws-ebs-csi-driver/pkg/driver.NewDriver({0xc00073ff18, 0xa, 0x4?})
	/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/pkg/driver/driver.go:99 +0x425
main.main()
	/go/src/github.com/kubernetes-sigs/aws-ebs-csi-driver/cmd/main.go:64 +0x4da
###
...

  ENDLOG for container kube-system:ebs-csi-node-vdcwm:node-driver-registrar
  Oct 26 14:15:26.196: INFO: Logs of kube-system/ebs-csi-node-vdcwm:liveness-probe on node i-07b3d93dec6e3f366
  Oct 26 14:15:26.196: INFO:  : STARTLOG
  W1026 14:00:04.692838       1 connection.go:173] Still connecting to unix:///csi/csi.sock
  W1026 14:00:14.692979       1 connection.go:173] Still connecting to unix:///csi/csi.sock
  W1026 14:00:24.693685       1 connection.go:173] Still connecting to unix:///csi/csi.sock
  W1026 14:15:24.692814       1 connection.go:173] Still connecting to unix:///csi/csi.sock

  ENDLOG for container kube-system:ebs-csi-node-vdcwm:liveness-probe
  [FAILED] in [SynchronizedBeforeSuite] - test/e2e/e2e.go:242 @ 10/26/23 14:15:26.196
  << Timeline

  [FAILED] Error waiting for all pods to be running and ready: Timed out after 600.000s.
  Expected all pods (need at least 0) in namespace "kube-system" to be running and ready (except for 0).
  25 / 26 pods were running and ready.

[torredil]

/retest

[torredil]

/retest

[torredil]

/retest

[ConnorJC3]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ConnorJC3

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 [ConnorJC3]

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

[AndrewSirenko]

/lgtm

[torredil]

/test pull-aws-ebs-csi-driver-external-test-eks

[torredil]

Need to request a NATGateway quota increase:

2023-10-26 18:01:04 [✖]  AWS::EC2::NatGateway/NATGateway: CREATE_FAILED – "Resource handler returned message: \"Performing this operation would exceed the limit of 5 NAT gateways (Service: Ec2, Status Code: 400, Request ID: 813d64cd-fecc-4b79-9831-86da84e28989)\" (RequestToken: 3a961337-8a6d-6e8d-4c45-290ba9e92dc9, HandlerErrorCode: ServiceLimitExceeded)"

[torredil]

/test pull-aws-ebs-csi-driver-external-test-eks

[AndrewSirenko]

/retest

[AndrewSirenko]

/retest

[ConnorJC3]

I'm going to try testing 1 at a time to try to dodge the quota

/test pull-aws-ebs-csi-driver-external-test-eks

[AndrewSirenko]

/retest