Exclude iso8601 version 0.1.7

The iso8601 package had a 0.1.7 release on October 19th.
Unfortunately, it cannot be installed under Python 3.3 due to a
unicode character in its README.rst, which is read by its
setup.py.  This causes our py33 gates to fail.  The temporary
solution is to exclude 0.1.7.  As a more permanent solution, I
have reported this as a bug[1] to the iso8601 developer, which
should hopefully result in a fix.

[1] https://bitbucket.org/micktwomey/pyiso8601/issue/10/setuppy-broken-for-python-33

Change-Id: Icdd8223b26caf755c8d6cd4c27c99ecea5f54a75
Adopt 0.1.8 as iso8601 minimum version

In the images api, we depend on iso8601 to parse some dates and times.
Recently, since version 0.1.4, python-iso8601 added support for a few
more formats, and we finally got some other issues nailed down by 0.1.8.
If end user switch from 0.1.8 back to 0.1.4 in the deployment, the image
api will lose support for certain datetime formats like YYYY-MM-DD
(where the time part is assumed to be all zeros). This obviously creates
a compatibility concern.

We were resolved to make glance compatible with both iso 0.1.4 and
0.1.8, but it appears that to do so requires essentially reimplementing
a large swath of iso8601 0.1.8 in glance itself.

Fixes bug: 1242501

Change-Id: Iece0116d3c412216251e2d7fbffe10bfe2c1c789
Signed-off-by: Zhi Yan Liu <zhiyanl@cn.ibm.com>
Switch to Hacking 0.8.0

Move requirements to Hacking 0.8.0

Change-Id: I8abb0e4c143b08f44b0f52806c4fb8cfa16765ed