* update to hex_core for hex-v2 repo support (#1865)

* update to hex_core for hex-v2 repo support

This patch adds only single repo hex-v2 support through hex_core.
Packages no longer filtered out by buildtool metadata and the
package index is updated per-package instead of fetched as one
large ets dump.

* tell travis to also build hex_core branch

* support list of repos for hex packages (#1866)

* support list of repos for hex packages

repos are defined under the hex key in rebar configs. They can be
defined at the top level of a project or globally, but not in
profiles and the repos configured in dependencies are also ignored.

Searching for packages involves first checking for a match in the
local repo index cache, in the order repos are defined. If not found
each repo is checked through the hex api for any known versions of
the package and the first repo with a version that fits the constraint
is used.

* add {repos, replace, []} for overriding the global & default repos

* add hex auth handling for repos (#1874)

auth token are kept in a hex.config file that is modified by the
rebar3 hex plugin.

Repo names that have a : separating a parent and child are considered
organizations. The parent repo's auth will be included with the child.
So an organization named hexpm:rebar3_test will include any hexpm
auth tokens found in the rebar3_test organization's configuration.

* move packages to top level of of hexpm cache dir (#1876)

* move packages to top level of of hexpm cache dir

* append organization name to parent's repo_url when parsing repos

* only eval config scripts and apply overrides once per app (#1879)

* only eval config scripts and apply overrides once per app

* move new resource behaviour to rebar_resource_v2 and keep v1

* cleanup use of rebar_resource module and unused functions

* cleanup error messages and unused code

* when discovering apps support mix packages as unbuilt apps (#1882)

* use hex_core tarball unpacking support in pkg resource (#1883)

* use hex_core tarball unpacking support in pkg resource

* ignore etag if package doesn't exist and delete if checksum fails

* add back tests for bad package checksums

* improve bad registry checksum error message

This requires some fancy dynamic work since the logger is started as
part of the kernel and we lost the sys.config from users when working
from there.

We start conservatively by making it an optional thing, turning it on
only where we know it to be safe.

The changes are applied _after_ having loaded the rest of configs so if
an inoffensive error happens, the shell works (with a bad error message)
rather than plain exploding.

Turns output like this:

    ===> Compiling apps/c/src/c.erl failed
    apps/c/src/c.erl:3: can't find include lib "parse_trans/include/codegen.hrl"

Into:

    ===> Compiling apps/c/src/c.erl failed
    apps/c/src/c.erl:3: can't find include lib
    "parse_trans/include/codegen.hrl"; Make sure parse_trans is in your app
    file's 'applications' list

Which is likely going to help newcomers encountering issues.

- added type specs for following private functions:
    - run/1
    - set_options/2
    - test_state/1
    - safe_define_test_macro/1
    - test_defined/1

- resolves #1645

Allows override of apps specified in other on-disk options. Equivalent
to `--apps=""`

Fixes #1785

As requested in #1733

Also small output fix in rebar3 shell

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

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.

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

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

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.

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

Fixes #1767

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

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.

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.

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.

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.

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