[BUGFIX] Fixed issue #255 ConfigurationLoader::loadPluginConfig() bug
[BUGFIX] Fix for git checkout based n98-magerun installation without composer.
[FEATURE] Merged pull request #251 Improve db:info with prefix and machine-readable output
[TASK] Added test and documentation for new db:info argument "setting".
[TASK] Updated composer file.

[skip ci]
[TASK] Updated changes file.

[skip ci]
[TASK] Updated changes and composer lock file.

[skip ci]
[TASK] Updated composer file.

[skip ci]
[FEATURE] Added --skip-config option

[skip ci]
[FEATURE] Issue #196 New table group for db:dump: --strip="@search"

[skip ci]
[FEATURE] Issue #124 Feature Request: dev:log:size should support "human readable" flags.

[skip ci]
[TASK] Updated phar file release candidate for release 1.83.0
[BUGFIX] Issue #256 Configuration value decryption fails when using Enterprise Edition
[TASK] Updated phar file.
[TASK] Updated changes file

[skip ci]
[TASK] Fixed wrong docblock.

[skip ci]
Merge branch 'release/1.83.0'

Conflicts:
	version.txt
Grammar police
Move the /tmp/magento/var warning to stderr

This warning, while useful in interactive usage, complicates things in
script. Errors/warnings belong in stderr, especially if a command can
finish it's task succefully.

This fix was prompted by using n98 in a cron script, like so:
    #!/bin/sh
    # ...
    prefix=`n98-magerun.phar db:info prefix`
    n98-magerun.phar db:query "TRUNCATE ${prefix}core_url_rewrites;"
    # ...

This generated an SQL syntax error.

TODO:
- There may be more cases where warnings should be moved to stderr.
- Investigate if the formatter can be extended to automatically route
  <error> tag to OutputInterface::getErrorOutput() for a better fix.
Merge pull request #264 from melvyn-sopacua/develop

Grammar correction and send warning to stderr