Escape logged HTTP data before token replacement

Problem: when LOG_DATA is on and LOG_TOKEN is off, kamaki logs HTTP
data, replaces the token (if it is included in the data) and then
escapes them to prepare for safe logging. If the data is non-ascii,
replacing raises a unicode error.

Solution: escape data before replacing the token.
Check server status before changing it

Fixes grnet/kamaki#57

This fix affects the CLI commands "server_start", "server_reboot"
and "server_shutdown" which are specified in "kamaki.cli.cmds.cyclades".
These are the operations that modify the status of a server.

The problem was caused when the target status was the same as the current.
In this case, the request for status modification would fail with a 400
error code response. At this point, kamaki didn't have adequate information
to correctly evaluate the error.

This problem is solved by checking the current status before attempting to
modify it.
Update general information and setup instructions

Refs #49
Write a set of short scripts using the kamaki lib

Refs #49