Provider name `capa` should become `aws`

[marians]

Status Quo

In various components of our platform, we have started differentiating between two provider names aws and capa.

• aws: our AWS platform before moving to Cluster API
• capa: our platform based on Cluster API provider AWS.

Likewise, we have differentiation between azure and capz.

Goals

• We want a consistent provider naming system which is easy to understand for end users.
• The platform generation pre CAPI vs. CAPI should not be expressed in the provider name.
• The commonly used cloud provider name should be used as Giant Swarm's provider name.

For context, here is the complete list of intended cloud provider names in the Giant Swarm platform (first column):

Intended Giant Swarm name	Cloud provider name	Cluster API provider name	Cluster API provider abbreviation
aws	AWS	Cluster API provider AWS	CAPA
azure	Microsoft Azure	Cluster API provider Azure	CAPZ
gcp	GCP	Cluster API provider GCP	CAPG
openstack	OpenStack	Cluster API provider OpenStack	CAPO
vsphere	vSphere	Cluster API provider vSphere	CAPV
cloud-director	Cloud Director	Cluster API provider Cloud Director	CAPVCD

Details

An incomplete list of places/artifacts that are affected:

• Cluster app repository name
• kubectl gs template cluster --provider PROVIDER
• Provider name reported by athena
• Prometheus metrics labels
• Grafana dashboard names and query labels
• opsctl list installations --provider PROVIDER (internal tooling)

[nprokopic]

In which places you would like to change capa to aws?

I guess we can rename capa to aws wherever we can, once all clusters have been migrated, but IMHO we cannot do it before the migration is completed, because currently there are more than few differences between capa and aws and I believe that our internal tooling usually assumes that aws is vintage AWS, and that capa is CAPA AWS.

e.g. aws-app-collection is the MC app collection for vintage AWS and capa-app-collection is the MC app collection for CAPA AWS, and those collections are not the same. It is similar in other places where we have something for both vintage AWS and CAPA AWS. Maybe we can rename capa to aws in some of those places, but it should be done carefully.