Carla (the SRE) would like ~an operator~ a process to generate a ConsoleLink for the installed tools

Currently, we generate the ConsoleLink when the tools are installed and the tool config is created. There are several challenges with this approach: 1) Cannot all be done declaratively because the ConsoleLink needs the url from the route after it has been created OR needs to know the ingress subdomain so that the url can be derived and 2) ConsoleLink is a cluster resource which requires the tool install to have more privileges than would otherwise be necessary, 3) the cluster resource created when the tool is installed creates contention when doing automatic validations of the deployment

Two options:
1) Operator watches for an annotation provided on the Route. If it is present then the ConsoleLink is created
2) Custom resource that generates the console link (and possibly the Route)