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

de-duplicate dependency list in rebar_compiler_erl.erl

Fix reloading logger_level

OTP kernel application use "logger_level" configuration for configuring
level in primary configuration.
rebar3 uses "logger_info" for this purpose - ths is little bit confusing
and probably mistake.
This commit will unify behavior between kernel and rebar3o

Fixes: 0303567d95 ("Reload logger config in shell")

rebar3 dialyzer: Warn when debug_info is disabled

keep resources in new state used in plugins upgrade

Fix crash when a dependency is missing app.src file

Fix custom compiler mods typespecs, add edoc

Ensure EDoc opts in umbrella apps are respected

Patch up and add tests on #2112

Bump cth_readable to fix lager on OTP-21+

This adds an additional loading and merging of options for EDoc using
the values from the top-level along with those specified in the
rebar.config of an umbrella application.

The app-specific config values are prepended to the global ones; this
can likely cause some problems with manual path handling, but is
unlikely to happen in practice and the rest seems to work fine based on
order

Fixes the issue in #2114

Support rebar config dir env var

Make missing file report more comprehensive

Warn when there's mismatch between rebar.lock & original package checksum

Gracious loading of unloaded but blacklisted mods

Only lint app files when compiling

try CIRRUS_TAG != '' for triggering cirrus for new tags

This allows to reduce the number of noise to only checking deps' app
files when they're built, rather than on every run.

Since main apps and checkouts are still compiled every time, the linting
takes place there and then with a higher frequency.

rebar3's shell allows people to set applications as blacklisted to
prevent them from being reloaded because that can cause crashes.
However, as part of its normal operations, rebar_paths unloads all
modules that are currently not "owned" by at least one process,
considering them safe to do so.

These two behaviours, put together, lead to an odd thing where some
modules are suddenly unloaded and not in path, and that can be
confusing.

This calls for a unification of both features. We could decide to be
pushing the complexity of rebar3's shell into rebar_path so it knows of
blacklists, but this would be a bad idea because rebar_agent already
owns all the damn hack.

So instead this fix adds an optional call within rebar_agent's
blacklisted applications handling that calls `code:ensure_loaded/1` on
their modules. This avoids forcing any code change that would cause a
crash, but reinstates unloaded paths that could be confusing.

Addresses some comments in #2013

bump relx to 3.32.1 and providers to 1.8.1

add support for usage message after template is done

fix install of s3cmd for publishing releases in cirrus

upgrade ssl_verify_fun to 1.1.5