`topydo revert` will search for backup corresponding with current state
of todo file, and use it to recover previous state. Output will show to
user results of which command had been reverted. If no suitable backup
is found (for example if user edited todo file recently with other
application), no action is taken and user is notified on the output
about lack of corresponding backup in backup file.

Backups containing whole todolist and archive can be now saved after
execution of each "read-write" command. Furthermore this change creates
base for eventual "revert" command.

Backups are safely stored and indexed in our own JSON-based format which
is compatible with python2.x and python3.x. We also use zlib compression
to minimize size of backup file. Path of the backup file is always
relative to the todo file, so backups from different todo files won't
mix up.

User can configure number of stored backups with new config option -
"backup_count". Any positive number will tell topydo to store that very
number of backups. Setting "backup_count" to 0 will completely turn off
backup functionality.

This will be used to recreate TodoList from a list of Todo objects.

Style Changes

Fix Wheel building

Evaluate conditional requirements at install time rather than compile time.

First line should end with a period

No blank lines allowed after function docstring

1 blank line required after class docstring

Allows monitoring to see how close we are to supporting these on these
platforms.

Sorted using `isort`. Sorted alphabetically, with sections for standard
library, third-party, and then internal imports.

comparison to None should be 'if cond is None:' or 'if cond is not None:'

statement ends with a semicolon

the backslash is redundant between brackets

line too long (> 79 characters)

blank line at end of file

too many blank lines

expected 2 blank lines, found 1 (above module level defined classes and
functions)

expected 1 blank line, found 0

blank line contains whitespace

trailing whitespace

at least two spaces before inline comment

missing whitespace after ':'
missing whitespace after ','

missing whitespace around operator

multiple spaces before operator

whitespace before ':'

whitespace before ')'

whitespace after '('

continuation line under-indented for visual indent

continuation line over-indented for visual indent

continuation line with same indent as next logical line

This allows the default discover on unittest to work