OTP-24 Readiness

fix injection of cth_readable to allow for hook configuration

This does not get rid of all warnings.

This fixes the HiPE dependency to be conditional to whether dialyzer
actually requires it or not, and makes use of the .app.src.script
feature internally, at build time. This may cause issues for scripts
built prior to OTP-24 being used for OTP-24 versions as it will ask for
apps that aren't in place, but there's no good work-around for that.

This also bumps the erlware-commons version to one that eliminates some
warnings, and makes the bootstrap script honor the warnings_as_errors
value of dependencies to allow the build to proceed until parse_trans is
fixed upstream.

as it won't be available. While at it, log errors and more relevant
resolution information at debug level.

and use it to avoid a warning in ./bootstrap.

Replaces (deprecated in OTP 25) http_uri calls with uri_string.

Fixed link to list of plugins.

Apparently the docs at rebar3.org do not contain the list of available
plugins - the docs at rebar3.readme.io do.

rebar_compiler: fix DAG and speed-up analysis for large repositories

This patch fixes incorrect behaviour of rebar_compiler_epp that
finds dependencies in _build/test/lib/... folder when rebar3 is run with
test profile. It is caused by code:lib_dir() pointing to _build
directory (when ebin is added to code path). Problem originates in
OTP that expects "include" and "ebin" directories being next to each other,
but rebar3 separates build artifacts and include files.

This patch also significantly speeds up analisys, caching file-to-application
mapping and avoiding repeated lookup for the very same gen_server/...

use newest certifi release

bump relx to v4.2.0 and rebar3 version to 3.14.3

Add support for relx config file

create release and upload escript for new tags

output relative paths in dialyzer provider

bump relx to v4.1.0

Prevent dialyzer warnings on OTP 23

We adapt .gitignore to the new vendored folder, also

1. we now rely on $1's vendor.sh script (instead of duplicating it here)
2. we assume that hex_core is rebar3-compatible
3. we rely on TARGET_ERLANG_VERSION
4. we generate exactly what was previously generating, while targeting a specific Erlang/OTP vsn

(some are not "wrong" per se, but incomplete)