they would always be left unfound otherwise.

Listed applications are simply ignored.

Allows for configuration time sub-application building.

Lock forwarding is what happens when the file on disk are on a different
version from what is specified in the lock file. Files on disk should be
updated to respect what's in the lock file.

A negative test has been added so that lock files that are outdated vis.
the underlying git and packages but match files on disk do not get
forwarded. This job is left to the `upgrade' command.

note that now ALL `src_dirs` across included profiles are
compiled. previously only the last included profile's `src_dirs`
were used

like `src_dirs`, `extra_src_dirs` are directories to be copied to
the `_build` dir and compiled. unlike `src_dirs` they are not added
to the .app specification

- The rebar package index files have been moved off the default path and
  will require a new `rebar3 update`
- Caching of downloaded packages automatically takes place in a path
  relative to the CDN used
- The cache path is not shared with hex as we now write and modify data
  in there arbitrarily
- Basic tests plus the working set for more of them is included

to prevent any data from being overwritten

fixes #395

Should fix #360

Allows to remove entries from the lock file, or the lock file as a
whole.

When fetching dependencies for the first time using a profile (`rebar3
as prod release` or `rebar3 ct`), the dependencies get fetched into the
non-default profile. This has two consequences:

- the files get re-downloaded on follow-up runs
- the lock file includes incomplete or too many deps in its list

This patch forces dependencies in the default profile to be stored in
_build/default/lib even when running under other profiles, then symlinks
them to the correct one.

This makes it so common dependencies in 'default' be downloaded there
and avoids re-downloading them. Should also fix the lock issues.

alongside their source (ie, if `some_tests` is a directory that
contains test suites beams resulting from compiling them will be
placed in `some_tests` in the appropriate `_build` directory

to the appropriate `_build` dir

matching directory paths

run subsets of test suites

test utils and add better eunit tests

Add test case to exercise the eunit provider using the test profile