new feature: deduct settings from remotes

[elonderin]

currently all settings need to be config'ed per project. If u have like 50 projects already checked out , that is very tedious. (come on! We are in a microservice era)

What speaks against deducting the settings from the remote URL with some heuristics/parsing of responses?

This could also include handling the base path problem in ticket #282

Because the current behavior is so obstrusive when nothing is config'ed, i'm going to uninstall this plugin, but would have loved it.