🌱 Print provider type and name to match config file naming

[benmoss]

What this PR does / why we need it:
Changes the log lines printed by clusterctl to be more helpful when trying to create config overrides.

I was head-scratching why my CAPI override was working but my CAPBK wasn't:

providers:
- name: "cluster-api"
  url: "https://github.com/benmoss/cluster-api/releases/latest/core-components.yaml"
  type: "CoreProvider"
- name: "bootstrap-kubeadm"
  url: "https://github.com/benmoss/cluster-api/releases/latest/bootstrap-components.yaml"
  type: "BootstrapProvider"

Fetching File="metadata.yaml" Provider="cluster-api" Version="v0.4.0-rc.1"
Fetching File="metadata.yaml" Provider="bootstrap-kubeadm" Version="v0.3.10"

I inferred from the log lines that the correct "name" for CAPBK would be bootstrap-kubeadm, since cluster-api was the right name for core CAPI.

This changes it to print out the correct name and the provider type as well, so users can more easily infer what they need to put in their override config.

Fetching File="core-components.yaml" Provider="cluster-api" Type="CoreProvider" Version="v0.4.0-rc.1"
Fetching File="bootstrap-components.yaml" Provider="kubeadm" Type="BootstrapProvider" Version="v0.3.10"
Fetching File="control-plane-components.yaml" Provider="kubeadm" Type="ControlPlaneProvider" Version="v0.3.10"
Fetching File="infrastructure-components.yaml" Provider="kubemark" Type="InfrastructureProvider" Version="v0.2.2"
Fetching File="infrastructure-components-development.yaml" Provider="docker" Type="InfrastructureProvider" Version="v0.3.10"
Fetching File="metadata.yaml" Provider="cluster-api" Type="CoreProvider" Version="v0.4.0-rc.1"
Fetching File="metadata.yaml" Provider="kubeadm" Type="BootstrapProvider" Version="v0.3.10"

[benmoss]

/area clusterctl

[fabriziopandini]

/lgtm

[CecileRobertMichon]

/approve
/milestone v0.4.0

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: CecileRobertMichon

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• cmd/clusterctl/OWNERS [CecileRobertMichon]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment