treecompose: add ability to output rhev and vsphere images

Requires new imagefactory-plugin deps and versions in spec.

Treecompose will now output multiple image flavors.  They are:

    * kvm (qcow2), raw, rhev (ova), vsphere (ova)

The above images will be the default outputs. If you pass a -i or
--images, you can override the ouputs.  For each image desired, you
pass an additional -i.  Treecompose will always output a qcow2.

For now, treecompose will require the default oz image_type to be raw
because imagefactory (for now) requires this for input on image
conversation.  When that is fixed, we then make raw no longer required.

Additionally, the -c option is no longer required. If not provided,
we look for config.ini.

And finally, there a some new exit conditions for treecompose.  We now
check the oz config for the image_type and a minimum RAM recommendation.
If those are not met, the script will exit with a stdout error message.
This is done so that consumer tools like koji/brew have the error at the
ready.
Release 2014.104
treecompose: Support the new ostree --output-repodata-dir
Allow 1.2.3 versions as well as 1.2.3.4

Also make refresh and minor autoversions have a blank cve instead of 0.
treecompose: s/--version/--versioning

--version already has a well known meaning for programs, let's call
this --versioning.
Release 2014.105
Remove old demo GPG key

Nothing should be using this anymore.
Fix missed line from previous version -> versioning commit
installer: Exclude systemd-container

This is a new package that may show up, let's just hardcode excluding
it for now.  It definitely won't work in an installer environment.
imagefactory: Output compat=0.10 qcow2 by default

So it can be read by RHEL6 era qemu.  Anyone who wants to take
advantage of the later format version can convert it when importing
into their infrastructure.
git hooks, plus revamp of trigger mechanism

I'd like to redefine the current mechanism for
event-driven composes. Please begin with doc/event-driven.md
and please provide feedback.
script to monitor journald

We now have two monitor processes: one for message bus,
one for git commits. Add a third one which will monitor
those two, then decide whether to trigger a build based
a particular config file (i.e. a particular compose tree).

This is an instance service: multiple ones can be running
at the same time, one for each /srv/PATH
build-monitor: no longer need trigger_command

...because we now log _all_ newRepo messages, and leave
the decision-making to someone else.
review feedback from cgwalters:

1) use journalctl --output=json. It's one line per message,
   so there's no issue with multiline reads.
2) safer SIGALRM handler.
Release 2014.106
imagefactory: Add a comment for compat=0.10
packaging: Require rpm-ostree
imagefactory: Do conversion in correct place
create-vm-disk: Add --origin-url argument

For OS vendors who are ready to provide online updates out of the box
(without post-install configuration), this makes it easy to create a
VM image which has the origin URL hardcoded.
installer: Quote % to avoid interpretation as a format character

I didn't know Python argparse docstrings were actually formats.