Helios issues moved

Hello!

This is mail for those who contribute to amber and thus use the git
version from master.

tl;dr: Helios will be reorganized. Hold your coding until its done or
commit/push/PR your contributions now.

I had a talk with Nico, after which I started to integrate changes
leading to release 0.13.0. First of these changes is removal of
amber.js, introduction of `amber config` mapping builder tool (which
builds mapping into config.js file and that file is to be loaded instead
of amber.js). `amber config` is already present is cli, and amber repo
master is already moved to used config.js built by `amber config`, as
you can see in internal/index.html.

MORE IMPORTANTLY, second change. With `amber config` configuration
builder, it is now easy to decouple Helios into its own repo. It is
planned to be done in these days, as soon as it is viable. Those of you
who contribute to Helios, either wait for a while until you do changes
to the code, or commit, push and PR them now, or find a way how to port
them (using patch format, for example). After the move, the helios code
will be the same, the namespace will be the same, just files will be
part of different repo with independent lifecycle.

Extracted Helios, being repo of its own, will be devDependency of amber
projects. For development of amber, the plan is to include it as a
submodule in external/helios directory (I know submodules are hard to
use, there is an alternative of putting another directory, ie my, in
.gitignore and letting the developer clone/push any version of Helios
he/she currently works on into my/helios, but this needs hand-cloning so
it does not work out of the box, submodules OTOH make it hard to use
your own fork of Helios; what would you prefer?).

Herby