fixes an issue when shell is terminated with an error "Bus error: 10",
on attempt to run rebar shell with verbose logging

Officially drop Erlang R16B support—Logger support in cth_readable, and compact CT output

Required for the Logger interface to be supported since it relies on
maps

cth_readable 1.4.0 supports the new logger interface from OTP-21, which
likely breaks compatibility with R16 builds.

It also includes a new compact interface, displaying output such as:

    ===> Running Common Test suites...
    %%% rebar_alias_SUITE: ......
    %%% rebar_as_SUITE: ...........
    %%% rebar_compile_SUITE:................................
    ............................
    %%% rebar_compile_SUITE ==> test_name: SKIPPED
    %%% rebar_compile_SUITE ==>
    {tc_user_skip,"compile:env_compiler_options/0 available"}
    ..
    %%% rebar_cover_SUITE: .............
    %%% rebar_ct_SUITE: ....................................

Allowing to display more tests within less screen space.
This mode has been added to the ct_readable option under the name
'compact' (now supporting true | false | compact), and has been made
default for rebar3.

Re-disable debug_info on prod profile

Had mistakenly only disabled it for deps.

Work around OTP-21 deprecation of get_stacktrace() and other incompatible changes

see https://github.com/erlang/rebar3/issues/1774

Based off a macro by @okeuday at https://github.com/erlang/otp/pull/1783

ensure dest exists before copying to it and fix src_dirs symlinking

Priv and include dirs need the virtual symlink in order to preserve hook
functionality in some edge cases.

This would cause crashes on linux and force people to have a src_dirs
config that is strictly matching what is on the file system rather than
acting as a specification of those that are valid.

To compare, if lib_dirs worked the same, then any repo that did not both
have apps/ and lib/ would crash, as the spec mentions both options as
valid.

Display warnings when cache dirs are read-only

This should provide more help to users directly and avoid having them go
through opening tickets for help.

Fixes #1767

Clear all dialyzer errors

- this is done by adding a HiPE dependency
- also in this: adding a test for directories, and fixing some indent

Bump cth_readable to 1.3.4: restore eunit macro formatter

Reload apps running in shell with new config

Fix local upgrade etag handling

Since packages store etags on disk directly, the local install feature
can no longer depend on this; we instead port the etag feature back to
local providers only.

This patch makes it so that whenever the rebar3 shell has a new
configuration for an application that is already running and would be
restarted (without risking the stability of the node or functionality of
rebar_agent), we stop and restart the app.

Fix precedence rules of erl_opts for test profile

When adding the 'TEST' macro to the test profile, we mistakenly sourced
the erl_opts values from the base profile rather than the test profile
itself.

This means that in cases where the base profile set an option such as
'no_debug_info' and a profile overrode it with 'debug_info', the default
options would get injected within the test profile, and broke the
precedence rules, yielding incompatible values.

This patch fixes things by adding the macro to the values sourced from
the test profile itself, fixing the issue.

Display script errors

Let's bundle this with another PR

This will at least display the script that failed with the stacktrace
before failing as usual, but without altering the return value.

This should make the common failure path more user-friendly without
breaking any existing behaviour that may have relied on the script file
working. If there's any unexpected side-effect, it will be visual only
rather than blocking full builds if ?ABORT were used.

Fix various Dialyzer warnings

Some still remain from erl_type calls from Dialyzer, but most of them
are handled.

Decided to just ignore rebar_alias since playing with the type specs of
abstract code format is just a nightmare and hard to do cross-versions I
guess.

Handle Schema-less Proxy URLs in ENV vars

We can probably still move ahead without a cache if we must

We've had multiple tickets opened because of unclear PROXY settings when
the scheme is missing form the URI. To be helpful, we instead add them
dynamically whenever they're missing.

Example issues:
- https://github.com/erlang/rebar3/issues/1747
- https://github.com/erlang/rebar3/issues/1697