Refactor console and swing impls of configurator to share state implementations

The console and swing implementations have completely different approaches to how they manage the configuration state of the application. They attempt to implement that same logic in two different ways, sometimes succeeding and sometimes failing miserably.

In extreme cases (like getUrl and setSettings) methods with the same name have dozens of different implementations with a variety of arguments with subtly different purposes strewn throughout the code base.

Finally, the console implementation is more or less monolithic, making it
very difficult work on.