Installer does not always add router CA to kubeconfig

The installer has logic that avoids adding the router CAs to the kubeconfig if the console is not available.  It's not clear why it does this, but it means that the router CAs don't get added when the console is deliberately disabled (it is now an optional capability in 4.12).

Seen in 4.12+4.13

Always, when starting a cluster w/o the Console capability

1. Edit the install-config to set:
capabilities:
  baselineCapabilitySet: None
2. install the cluster
3. check the CAs in the kubeconfig, the wildcard route CA will be missing (compare it w/ a normal cluster)

router CAs missing

router CAs should be present

This needs to be backported to 4.12.