Context: The installer passes the custom service endpoint to CAPA and cluster operators.

Since the service name in each custom endpoint entry is loosely defined, the consuming components might decide to change the way it identify a service to apply the endpoint URI. For example, CAPA is planning to do use the new ServiceID field in v2: https://github.com/kubernetes-sigs/cluster-api-provider-aws/blob/456f00d23a3584c677ef8100175c84fed91e8bb2/pkg/cloud/endpoints/endpoints.go#L124-L139 

This can potentially cause the endpoint to not be applied at all. We need to investigate:

• Whether we can include duplicate endpoint entries (i.e. same URI) with both v1 and v2 service names.