bootstrap image: Add remote command execution script

In order to automate the complete bootstrap build process we need a
mechanism to control the second phase which builds the final packages
on the booted bootstrap Haiku. To avoid additional dependencies
(buildbot slave, ssh, rsh,...) we'd have to cross-build, there's now a
pair of simple python scripts that allows executing commands on a remote
machine. The server script (bootstrap_daemon.py) is added to the
bootstrap image and started automatically during the boot.

Use bash_bootstrap for the bootstrap build.

* don't build the in-tree bash.
* bash doesn't need to be a mandatory package, it's now a dependency of
the haiku package.

bash: use outsourced package for non-bootstrap builds.

* the bootstrap build keeps on building the in-tree bash.

Copy haikuports/FormatVersions onto the bootstrap image.

* Without it, haikuporter will believe there's a version mismatch
between itself and the haikuports tree.

Add files missing in last commit, sorry.

bootstrap image: Add remote command execution script

In order to automate the complete bootstrap build process we need a
mechanism to control the second phase which builds the final packages
on the booted bootstrap Haiku. To avoid additional dependencies
(buildbot slave, ssh, rsh,...) we'd have to cross-build, there's now a
pair of simple python scripts that allows executing commands on a remote
machine. The server script (bootstrap_daemon.py) is added to the
bootstrap image and started automatically during the boot.

Use bash_bootstrap for the bootstrap build.

* don't build the in-tree bash.
* bash doesn't need to be a mandatory package, it's now a dependency of
the haiku package.

bash: use outsourced package for non-bootstrap builds.

* the bootstrap build keeps on building the in-tree bash.

Copy haikuports/FormatVersions onto the bootstrap image.

* Without it, haikuporter will believe there's a version mismatch
between itself and the haikuports tree.

Add files missing in last commit, sorry.