uniform use of LAGOON_CONFIG_x variables across tooling

[tobybellwood]

Once uselagoon/build-deploy-tool#193 is merged and these variables:
LAGOON_CONFIG_API_HOST:
LAGOON_CONFIG_TOKEN_HOST:
LAGOON_CONFIG_TOKEN_PORT:

are available in all newly deployed environments the following logic should apply:

• lagoon-cli: should use these variables to create a default cluster config if none is provided in the ~/.lagoon.yml (priority TBA)

• lagoon-sync: should use these variables to connect to the SSH service and get a token to talk to the API, falling back to the ssh and api defined in the project .lagoon.yml (and if not there then ?amazeeio?)

• drupal-integrations: should use these variables to connect to the SSH service and get a token to talk to the API, falling back to the ssh and api defined in the project .lagoon.yml (and if not there then ?amazeeio?)

Are there other places - maybe some default tasks etc? Maybe other CLI tools?