[BUG] After applying new EKS integration Cloudbeat send errors regarding file configuration and cluster's name.

**Describe the bug**

When creating new KSPM integration with EKS cluster deployment (correct credentials provided), cloudbeat the following error logs appear:
```
19:02:34.025 elastic_agent.cloudbeat [elastic_agent.cloudbeat][error] Failed to parse file configuration for process kubelet, error -type is not supported
19:02:34.045 elastic_agent.cloudbeat [elastic_agent.cloudbeat][error] fail to resolve the name of the cluster, error unable to retrieve cluster identifiers
```

**Preconditions**
ELK Stack and EKS clusters are deployed

**To Reproduce**
Write the exact actions one should perform in order to reproduce the bug.
Steps to reproduce the behavior:
1. Create new KSPM integration
2. Select EKS Kubernetes deployment
3. Fill correct AWS credentials
4. Save and Continue
5. Add new agent and deploy to EKS cluster
6. Navigate to Fleet
7. Open agent logs
8. Filter dataset = elastic_agent.cloudbeat
9. Select log level = error

**Expected behavior**
There are no error logs regarding file configuration and cluster's name.

**Desktop (please complete the following information):**
- OS: NA
- Browser: NA
- Kibana Version: 8.6.0 Commit: 93183bddac40f8a7ee8e566d1651f9f3b586a520
- Endpoint Version: elastic-agent 8.6.0: 3bff6ff456946a30f5b743e6d36902e472c67e48
- Other Version: