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

By default rebar3 displays compiler sources as absolute paths in their
original location, which is under the build dir.

This change introduces an option 'compiler_source_format' to format
sources in two alternative ways:

    relative
    absolute

When either 'relative' or 'absolute' are specified, the file is
resolved to its original location when it is a link. When 'relative'
is specified, the path is displayed relative to the current working
directory. When 'absolute' is specified, the path is absolute.

The default value is 'unchaged' which leaves the compiler source
unchanged.

This is arguably too flexible as I suspect most people would opt for
'relative' all the time - it's the most compact representation of the
file and is sufficient to find the source given cwd. The change
however is meant to introduce the change gradually, preserving
existing behavior and giving users a choice for formats.

In time perhaps the default can be changed to 'relative' - but still
allowing users to revert to the other two options ('absolutel' and
'unchanged') as needed.

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

Dependent libs is required for some module when cover compiling.
So all dependencies should be available on code path.

This fixes #1148 issue.

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`

Extract dist config handling, support {dist_node, ...}