Enhance build tools to use team config

[t1m0thyj]

Currently new contributors must create a config.local.json file, used by the build tool for connection info.

If we enhanced the build tool to use team config, then the init command could check if team config exists. If yes, it could prompt for an SSH profile to use. If no, it could prompt for host, port, private key path, etc to create a profile.

We'd need to figure out how to handle the deployDirectory and goEnv properties - deployDirectory could move to serverPath property in the profile, and perhaps goEnv could move to a .env file.