OTP 23 [master] compatibility

add rebar_string:trim function for removing all leading/trailing whitespace

For OTP 19 and earlier compatibility.

This function was used for trimming the version from a `{file, File}` app
vsn in .app.src but caused a crash because it did not exist.

Switching to uri_string as the warning suggest
would ruin OTP 20 compatibility.

See [1] for context.

1. https://bugs.erlang.org/browse/ERL-1113

Switching to uri_string as the warning suggest
would ruin OTP 20 compatibility.

Add `--statistics` option to dialyzer command

In some cases its nice to have dialyzer statistics out of box without
any additional steps.

Fix epmd start on windows

Windows does not have the same quoting rules as Unix so
we need to use platform independent quoting. Also for
os:cmd like operations we do not expect the program to
read any input so in order for it to work on windows we
should put -noinput there.

Allow cleaning specific apps or deps only

Disable bbmustache escaping

This will allow project with larger dependencies sets to clean only the
apps they want to when testing or changing small things, rather than
forcing a rebuild of the whole dep set.

Also allows cleaning up apps, not just deps.

We never really need that and nobody would expect it either. We're
rendering normal files, not HTML.

Handle missing OTP apps better

Otherwise we only get silent failures. This has been fixed a while ago
in mainline rebar3 but never in the bootstrap script.

Support `profile_string` overlay var in releases

Reload logger config in CT suites

Fixes #2159; this is done by force-reloading the handlers to match the
config.
This can create a bit of a funny effect if sys.config specifies an INFO
log level (or lower) is specified. While apps are booted for config
changes before the cth_failonly hook is enabled, supervision and other
application log messages can start being output. They will start being
suppressed once the CT run begins.

This is not a bug, it's a race in instantiation of control and enabling
of log levels. Nothing we can do about that. It might however surprise
people a good bit. If non-default stdout handlers are added, they are
similarly likely to become noisy; specifying a test-specific sys.config
file may be necessary then.

Also includes a bump of cth_readable version, which now checks for
updates to the log formatter on every test output.

Disable the default logger handler in shell if required

Fix case clause which used wrong element order

See http://erlang.org/doc/man/ct_hooks.html#Module:on_tc_fail-4

To avoid a conflict the Kernel's default handler have to be disabled
before the new default handler is added

    {kernel,
     [{logger,
       [{handler, default, undefined}
       ]}
     ]},
    {my_app,
     [{logger,
       [{handler, default, my_handler, #{}}
       ]}
     ]}

To support this behavior in shell it's necessary to process the
handler-default-undefined tuple.

It's not clear what to do with the simple handler (logger_simple_h)
however.  It's added at the start and removed if a default handler was
added.  Should it be added in reread_logger_config/1 if there's no
default handler?

Fix a couple typos in readme

upgrade relx 3.33.0

format error from provider init and print as warning

support REBAR_BASE_DIR for setting the base_dir

Fixing duplicate macro definition in umbrella edoc

Update vendored in hex_core to version 0.5.1

When in umbrella mode (or through multiple profiles), users can specify
macros for EDocs based on either the {def, ...} or the {macros, ...}
arguments.

This patch replaces the prior options merging for umbrellas to use the
rebar3 tup_umerge utils to remove identical duplicates while preserving
correct ordering, and manually merges the {macros, ...} definitions
while ke eping the correct precedence rules since these appear (given
their behaviour) to be all individually extracted and passed as `{d,
...}` to  the compiler so that epp expands them. This compiler
function freaks out on any re-defined macros and explodes.

Do note that the macros with `{def, ...}` are edoc macros and do not
suffer from that issue, safely deduplicating multiple definitions.

version 0.5.1 is a maintenance release of hex_core specifically for
 rebar3 which contains a configuration update. Prior to v0.5.1 if no
 repo_organization key was set this could result in a function clause
 error. The behavior is to now set repo_organization to undefined in
 this case.

Repair edoc functionality on rebar3 itself