EKS cluster creation failing on Creating new workload cluster with folders with ' in them such as vm's

**What happened**:
When creating a cluster on my vmware cluster I can't make it past "Creating new workload cluster" if I attempt to provide a key format like ssh-ed25519

```
2022-04-22T18:13:04.132Z V4 ----------------------------------
2022-04-22T18:13:04.132Z V4 Task start {"task_name": "workload-cluster-init"}
2022-04-22T18:13:04.132Z V0 Creating new workload cluster
2022-04-22T18:13:04.132Z V5 Adding extraArgs {"cipher-suites": "TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256"}
2022-04-22T18:13:04.132Z V5 Adding extraArgs {"tls-cipher-suites": "TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256"}
2022-04-22T18:13:04.132Z V5 Adding extraArgs {"tls-cipher-suites": "TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256"}
2022-04-22T18:13:04.135Z V5 Adding extraArgs {"tls-cipher-suites": "TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256"}
2022-04-22T18:13:04.136Z V6 Executing command {"cmd": "/usr/bin/docker exec -i eksa_1650650965873548237 kubectl apply -f - --namespace eksa-system --kubeconfig sandbox1/generated/sandbox1.kind.kubeconfig"}
2022-04-22T18:13:07.955Z V5 Error happened during retry {"error": "error executing apply: error: error parsing STDIN: error converting YAML to JSON: yaml: line 12: did not find expected key\n", "retries": 1}
2022-04-22T18:13:07.955Z V5 Sleeping before next retry {"time": "5s"}
```
Which leads up to it generate dump files. But I can't seem to figure out what it is trying to apply here, or why it would be malformed.

**What you expected to happen**:
Succeed in this step or tell me what we are trying to apply if we get a conversion error (Or possibly what I could have malformed elsewhere causing this?)

**How to reproduce it (as minimally and precisely as possible)**:
Create a a default valid cluster yaml as per the docs and target a folder such as
vm's or vm's/k8s_vm's

**Anything else we need to know?**:

**Environment**:
eksctl 0.94.0
eksctl anywhere v0.8.2
vcenter 7.0.3.003
docker version: 20.10.14
host: ubuntu 20.04

Reproduce the failure with a cluster YAML targeting a folder such as vm's or vm's/k8s_vm's. Start with the workload-cluster-init logs and the generated dump files, then inspect the manifest passed to kubectl apply and the YAML reported at line 12. Done means apostrophes in the target path no longer produce malformed YAML, or the conversion error identifies the affected manifest and value.

Written by the indexing model from the issue text.