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)


parseDefaultPropertyFileFromResource(potentialPropertyFile);
                }
            } catch (IOException e) {
                throw new CommandLineParsingException(e);
            }
        }
    }
    /**
     * Open a property file that is embedded as a Java resource and parse it.
     *
     * @param potentialPropertyFile location and file name of the property file
     * @throws IOException                 if the file cannot be opened
     * @throws CommandLineParsingException if an error occurs during parsing
     */
    private void parseDefaultPropertyFileFromResource(File potentialPropertyFile) throws IOException,
            CommandLineParsingException {
        try (InputStream resourceAsStream = getClass().getClassLoader().getResourceAsStream
                (potentialPropertyFile.getAbsolutePath())) {
            if (resourceAsStream != null) {
                parsePropertiesFile(resourceAsStream);
            }
        }
    }
    /**
     * Open a regular property file (not embedded in a resource - use {@link #parseDefaultPropertyFileFromResource}
     * for that) and parse it.
     *
     * @param potentialPropertyFile path and file name to the the property file
     * @throws IOException                 if the file cannot be opened
     * @throws CommandLineParsingException if an error occurs during parsing