Follow WG Naming Recommendations on Master -> Control Plane

[gjtempleton]

Updating documentation references to master to control plane/API Server as appropriate as per https://github.com/kubernetes/community/blob/master/wg-naming/recommendations/001-master-control-plane.md

A number of example files are renamed to match this convention.

I've left explicit references to the current master taint where discussed as part of allowing the CA to run on a control plane node as this is deprecated, but not yet removed as per: kubernetes/kubernetes#95382

Fixes #3796

[mwielgus]

As many people may not be familiar what "control plane" node is (we have been using master for ages), please add something like (previously known as "master node") where applicable.

[gjtempleton]

@mwielgus It feels a bit messy to me, but I've added clarifying text anywhere I moved from master to control-plane along with some hidden TODO: stanzas to remind us to come back and remove these once k8s fully removes the terminology.

I've left anywhere that I changed from master to something more specific like API server as I feel that if they're unfamiliar with that terminology those terms should be easy enough to find more useful docs than previously.

[mwielgus]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: gjtempleton, mwielgus

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:

• cluster-autoscaler/OWNERS [mwielgus]
• vertical-pod-autoscaler/OWNERS [mwielgus]

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