Improve Node, Taints, and Tolerations concepts

- Use glossary shortcodes in Node concept
  Add glossary tooltips to help new readers take in unfamiliar concepts.
- Move minion hint to glossary
  The page about Node need not mention the former name (minion): it has
  been many releases since the name change.
  Instead, add a hint to the full glossary definition.
- Use note shortcodes where appropriate
- Order node management section first in concept page
- Drop list of components that act on Nodes
  With Operators and CustomResourceDefinitions now common, plus the
  cluster API, it's less easy to give a definitive list of components that
  interacr with Node objects.
- Tidy old mentions of GA features for Node
- Give node tainting by condition its own section
- Introduce toleration concept before using it
- Mention version in TopologyManager feature state
- Other rewording
- Tidy Node condition table
- Explain SchedulingDisabled synthesized condition
- Drop details of supported versions for NodeRestriction
  Assume that cluster version is v1.13 or later

content/en/docs/reference/glossary/node.md

@@ -15,3 +15,5 @@ tags:
 <!--more--> 
 
 A worker node may be a VM or physical machine, depending on the cluster. It has local daemons or services necessary to run {{< glossary_tooltip text="Pods" term_id="pod" >}} and is managed by the control plane. The daemons on a node include {{< glossary_tooltip text="kubelet" term_id="kubelet" >}}, {{< glossary_tooltip text="kube-proxy" term_id="kube-proxy" >}}, and a container runtime implementing the {{< glossary_tooltip text="CRI" term_id="cri" >}} such as {{< glossary_tooltip term_id="docker" >}}.
+
+In early Kubernetes versions, Nodes were called “Minions”.