Support images that can only be deployed by the user that registers
the image to cyclades

You don't need the account name. You can fetch it from astakos using
the authentication token.

The cow file when creating images or the temporary image file when
bundling the host system may be large. Allow the user to overwrite
the directory under which those files get created.

This reverts commit 883e57b0.
Drop the greenlet support.

Needed by new kamaki, otherwise it throughs an exception at the end.

Fix various typos in messages, add .gitignore file for
automatically produced intermediate files.

Fixed many `E127 continuation line over-indented for visual indent'
errors

This method returns a sysprep object with a given name. Now,
(enable,disable)_sysprep work with sysprep objects instead of sysprep
names

If no customization is to be applied the image should be mounted
readonly.

Let the application decide what to do with them. If image-creator
receives an error from kamaki it will terminate. But this may not be
the proper thing to do for an interactive application like
image-creator-dialog

The error function main.py used for outputing errors has been removed
and the code was not updated to use the error method of SimpleOutput
output class.
Also did a minor cleanup: git_os_class function was renamed to os_cls

If not then don't output progressbars and colors

All image-creator components now output messages using an instance
of one of the output classes.

The metadata are collected in the constructor and are saved in the
meta variable. This way they can be accessed and altered by the
sysprep methods. There are cases where some metadata are not valid
and need to be updated after a sysprep action is performed. For
example, remove_user_accounts sysprep action may remove a user that
is present in the USERS metadata.

The metadata passed by the user will overwrite any automatically
collected metadata with the same key.

If the swap partition is the last partition in the media, then it can
be safely removed. The image-creator will save enough info in the
SWAP metadata to recreate it.

This is needed because otherwise setup.py fails on some systems. Also
do some more cleanup.

Also rearrange input options

Also merge data_cleanup tasks with syspreps and did a major cleanup

Add --print-data-cleanup and --print sysprep input options. If enabled
the program will output what data cleanup and syspep operations will
and won't run a a selected input media