We have a liquibase command that looks something like this:

```sh
/liquibase/liquibase \
       --driver=org.postgresql.Driver \
       --changeLogFile="db.changelog-master.xml" \
       --url=<redacted> \
       --username=<redacted> \
       --password=<redacted> \
       update \
       -Dcoreschema="${core_schema}"
```

After upgrading the CLI from 4.3.3 to 4.4.0, it fails with the following error:

```
Unexpected argument(s): -Dcoreschema=public

For detailed help, try 'liquibase --help' or 'liquibase <command-name> --help'
```

Since the release notes state "this release should be 100% backwards compatible", I expect this is an oversight? Or is there a replacement for the `-Dproperty=value` syntax? I haven't found one looking through `--help` and the [property substitution docs](https://docs.liquibase.com/concepts/basic/changelog-property-substitution.html) at least.

The syntax can also still be found on https://docs.liquibase.com/tools-integrations/cli/home.html:

![image](https://user-images.githubusercontent.com/2620907/122090597-36d63400-ce08-11eb-92e8-d320cd5c5baa.png)


handler.setFilter(new SecureLogFilter(logService.getFilter()));
        }
        
        
        
        if (level != Level.OFF) {
            DeprecatedConfigurationValueProvider.setData(HubConfiguration.LIQUIBASE_HUB_LOGLEVEL, level);
        }
    }
    private static Level parseLogLevel(String logLevelName, ConsoleUIService ui) {
        logLevelName = logLevelName.toUpperCase();
        Level logLevel;
        if (logLevelName.equals("DEBUG")) {
            logLevel = Level.FINE;
        } else if (logLevelName.equals("WARN")) {
            logLevel = Level.WARNING;
        } else if (logLevelName.equals("ERROR")) {
            logLevel = Level.SEVERE;
        } else {
            try {
                logLevel = Level.parse(logLevelName);
            } catch (IllegalArgumentException e) {
                ui.sendErrorMessage("Unknown log level " + logLevelName);
                logLevel = Level.OFF;
            }
        }
        return logLevel;
    }
    /**
     * Warns the user that some logging was suppressed because the --logLevel command line switch was not set high