EKS Kubernetes related fetchers should use leader election

[ofiriro3]

Motivation
As a developer, I would like the EKS Kubernetes-related fetchers to be deployed once per cluster.

In-depth
Some of the EKS fetchers require Kubernetes resources before addressing the relevant AWS services.
Since the Kubernetes resources are mutual to all cloudbeat instances, fetching the K8s resources from all Cloudbeat instances will result in duplications.

To solve this issue, we need to use the same leader election lease when deploying the EKS Kubernetes-related fetchers.

Definition of done

• The EKS kuberenetes-related fetchers are deployed once per cluster.