Issue #999 Call WatchConfig in viper initialization

Since we initialize viper in root.go and the daemon runs that only once, new
changes to the config on a different process or by running `crc config`
commands are not known to the daemon this should make daemon aware of changes
made to the config file, after it has been launched.

pkg/crc/config/viper_config.go

@@ -101,6 +101,7 @@ func InitViper() error {
 	if err != nil {
 		return fmt.Errorf("Error reading configuration file '%s': %v", constants.ConfigFile, err)
 	}
+	v.WatchConfig()
 	globalViper = v
 	return v.Unmarshal(&changedConfigs)
 }