- the internal representation for package locks moves from `{Name, {pkg,
  PkgName, Vsn}, Lvl}` to `{Name, {pkg, PkgName, Vsn, Hash}, Lvl}`
- the internal representation for packages moves from `{pkg, PkgName,
  Vsn}` to `{pkg, PkgName, Vsn, Hash}`
- the hash can be `undefined`, meaning no check will be done
- no checking is done yet.

adjust `data_dir_correct` test in ct suite

don't bother checking the profile in the path to the data dir

filter available package versions individually by buildtools

deploy escript to travis releases instead of s3

Fix path command to consider {deps_dir, "deps"} in rebar.config

#1185 fix windows git working directory

fix issue #1185 git working directory issues due to command line options in Windows

don't needlessly update the code path twice if no hooks to run

don't generated coverage for `extra_src_dirs`

closes #1057 and #1179

fix otp-19 bootstrap compiling

upgrade erlware_commons for OTP-19 fix

Fix shell node startup

Add support for xref_ignores

Allows overwrite default cache dir using REBAR_CACHE_DIR

Fixes logging from remote shells in rebar3 shell

Add a provider hook for edoc

Change to new hex.pm repo URL

upgrade relx to 3.19.0

Allows `pre_hooks` and `post_hooks` to fire for the `edoc` provider.

Somehow swapping the tty handler once more fixes everything. I guess we
were missing a step somehow.

upgrade relx and erlware_commons

supported dist_node in ct and eunit

Recursively load configurations in shell

The sys.config loading in the shell command did not implement recursion
and thus processed the file different from a `erl -config cfg/path`.

Instead of reading every time that rebar_dir:global_cache_dir/1 is
called

Blacklist apps to reload

When an app contains one of the modules we can't afford to get upgraded
without breakage (i.e. erlware_commons, providers, getopt), skip
reloading that application from the rebar3 agent, such that it can keep
on working in subsequent calls.

Blacklisted:

- erlware_commons (broke on ec_cmd_log)
- providers (core to functionality)
- cf (useful to not explode on colors)
- cth_readable (only used for CT suites, but incompatibilities may break
  whole runs)

Fixed git version bug

I've tried to compile project with git in .app.src vsn
Project was tagged as 1.0.0, but resulting .app vsn becomes 1.0.0+build.6.reff0aec24

```git lg
* f0aec24 - (80 минут назад) Fixed ct — Kozlov Yakov (HEAD -> master, tag: 1.0.0, origin/master)
... 5 commits before
```

```
$ git log --oneline --no-walk --tags --decorate
f0aec24 (HEAD -> master, tag: 1.0.0, origin/master) Fixed ct
```

I've found that `HEAD -> master` doest match pattern in [rebar_git_resource](https://github.com/erlang/rebar3/blob/master/src/rebar_git_resource.erl#L204)

allow all `ct_opts` arguments to be passed through to `ct:run_test/1`