improve control plane access

[xh3b4sd]

Right now awscnfm relies on your local Control Plane connection setup and assumes your process environment is set up accordingly. This implies quite a limitation to the developer workflow because the connection management is not self contained. Other terminal sessions can magically change the connection. This should be improved and made self sufficient. Note that opsctl is doing that already, but the code is awfully complicated and involves Github Auth and Vault Auth. We need to find the common ground and have more sharable code different tools can use.