Auto reconfigure D3nver instance on config.yml changes

Currently, the only way to take changes from the `config.yml` file into account is to delete the D3nver inastance and `init` a new one.
If done properly, this is quick and easy because for just memory changes or any "non RBI" changes, you don't have to re-download a D3nver RBI and the init is nearly instant.

Would be great to have a mechanism where we keep the current state of the D3nver instance somewhere (some kind of shadow copy of the current config.yml) and as soon as there is a diff between this copy and the config.yml file, then we trigger a STOP/UNREGISTER/INIT/START cycle.