This commit replaces the method of upgrading by unlocking all transitive
deps by one that utilizes the parent element of each app to only
unlock transitive deps of children of the top level deps being upgraded.

Additionally the run function of upgrade_SUITE is modified to only create
the mock updates before the upgrade provider is run, instead of before
any provider is run, which would cause improper behavior in install_deps.

to `rebar_erlc_compiler`

`reduce_path/1` -> `canonical_path/1`
`relative_path/2` -> `path_from_ancestor/2`

this test almost certainly only fails under very limited circumstances
limiting it's utility. it is known to fail with some versions of rebar3
when this test is run via `rebar3 ct --cover`

add tests

Instead fetching and resolving src deps (which could depend on pkg deps)
and then pkg deps this patch combines the two into a single set of
iterations by level. The only difference between src and pkg deps in this
new install_deps is how their deps list is found -- from the config or
lock file for src deps and from the neighbors of the vertex for pkg.

Just rework the error message.

On a single app's dep list, the first noted wins if there's a duplicate
between packages and sources, rather than favoring source there anyway.

Requires a rework of other test suites using the same dep-handling
mechanism.

In the spirit of Original Rebar's "require_min_otp_vsn", this adds
rebar_utils:check_min_otp_version/1 (taking a string containing the
minimum version) and rebar_utils:check_blacklisted_otp_versions/1
(taking a list of regular expression strings), as well as tests in
rebar_utils_SUITE. They're currently only called by the tests-
how/where to best place calls to them from non-test code needs to be
determined (at which point two corresponding rebar.config keys can be
supported). For example, the version probably shouldn't be enforced when
just running "rebar3 help".