Moved package manager to standalone project.
Repackaged, moved bits back to editor.

Pacman is just going to handle getting packages onto your machine and built.
The editor can build on that and scan the installed packages for Scaled stuffs
(major and minor modes, plugins, etc. etc.). There's no especial value in
having that stuff in the package manager.
More explicit config file modeling.

After arguing with Paul about it all day, I felt the need to put my money where
my mouth was.
Fix mainClass.
Log and continue on invalid package.scaled.
Better error reporting.
Use PackageLoader everywhere, expose path.
More kibbles and bits.
Yet more revamping.

To avoid a bunch of annoying special casery, I'm going to have the JVM that's
running the package manager launch the editor directly. Then the editor will
just use the package manager as is to do its package stuffs.

I opted to make PackageManager a global singleton rather than pass it through
the editor's main() because the editor's main() is already greatly weirded by
the requirements of JavaFX Application. Meh.
Report source directly.
Search self first, then depends.

This all needs to be revamped, per the comment in MavenResolver, but this is
more correct for now.
Merged Package and PackageInfo.
Omit optional depends.
Put VCS in Source.
Rewrote whole shebang in Java.

Boy that's annoying. We also now use Capsule (which in turn uses Aether) to
handle Maven dependencies, which means we're doing things "properly" and also
that Maven dependencies will be downloaded from Central automagically.

A bunch of work remains to be done, and I need to sort out how I'm going to
deal with the fact that everyone needs to share the same scala-library and
guava depends. Oh the funs.
A new new approach to transitive depends.

A package inherits all Maven depends from its project dependencies (and omits
them from its own list). This means it is not possible to override a
subpackage's dependency with a different version, but that's basically
impossible anyway because someone else may have already resolved that
subpackage and *not* overridden its depends and it will have loaded the
non-overridden classes, etc. etc.

So a package has to be lord and master over its own transitive depends. So when
you depend on a package, you get the "whole package" so to speak. Hopefully
this will not be a giant fucking quagmire down the road, but we'll see.
Improve error reporting.
Disable depends-included jar gen for now.
Javadoc-ize.
Standard methods.

Oh the lack of case classes hurts.