Other providers' CRDs are installed

**What happened**:
When creating a cluster with CloudStack provider other provider's CRDs are also installed.
```
customresourcedefinition.apiextensions.k8s.io/snowdatacenterconfigs.anywhere.eks.amazonaws.com 2022-04-11T16:52:53Z
customresourcedefinition.apiextensions.k8s.io/snowmachineconfigs.anywhere.eks.amazonaws.com 2022-04-11T16:52:53Z
customresourcedefinition.apiextensions.k8s.io/tinkerbelldatacenterconfigs.anywhere.eks.amazonaws.com 2022-04-11T16:52:53Z
customresourcedefinition.apiextensions.k8s.io/tinkerbellmachineconfigs.anywhere.eks.amazonaws.com 2022-04-11T16:52:53Z
customresourcedefinition.apiextensions.k8s.io/tinkerbelltemplateconfigs.anywhere.eks.amazonaws.com 2022-04-11T16:52:53Z
customresourcedefinition.apiextensions.k8s.io/vspheredatacenterconfigs.anywhere.eks.amazonaws.com 2022-04-11T16:52:53Z
customresourcedefinition.apiextensions.k8s.io/vspheremachineconfigs.anywhere.eks.amazonaws.com 2022-04-11T16:52:53Z

```

I used this command to list all resources in the cluster
```
kubectl api-resources --verbs=list -o name | xargs -n 1 kubectl get --show-kind --ignore-not-found -A
```

[all-resources.log](https://github.com/aws/eks-anywhere/files/8474572/all-resources.log)

**What you expected to happen**:
Installing only related resources.

**How to reproduce it (as minimally and precisely as possible)**:
Create a cluster with CloudStack provivder
List all resources
Find capc or vsphere

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

**Environment**:
- EKS Anywhere Release:
- EKS Distro Release:

The report names no files or tests. Start by creating a cluster with the CloudStack provider, then run the provided kubectl api-resources command and inspect which provider resources are installed. Done means a CloudStack cluster installs only its related resources and does not include the listed Snow, Tinkerbell, or vSphere CRDs.

Written by the indexing model from the issue text.