Further break down CAPI template

**What would you like to be added**:

Further break down the CAPI template in each provider, based on resource type or business logic. Example break downs:
- Control Plane
- Worker Nodes
- Unstacked etcd
- Provider agnostic resources to share across different providers
- Provider specific cluster resource set
- ...

**Why is this needed**:

For each provider, we have one giant `template.yaml` that contains all the CAPI specs. PR https://github.com/aws/eks-anywhere/pull/264 breaks it down to `template-cp` and `template-md` so that we can separate the upgrade workflow by upgrading control plane before worker nodes.

The `template-cp.yaml` contains CAPI cluster, provider cluster, control plane, unstacked etcd, cluster resource set, etc. Further separation of the resources might be needed for clarity and better naming convention.

Compare each provider's template.yaml with the template-cp.yaml and template-md.yaml split described in PR #264. First map the CAPI resources and upgrade workflow represented in those templates; done means agreeing on a consistent resource-based breakdown and naming convention across providers, with the resulting templates separated accordingly.

Written by the indexing model from the issue text.