Fix 'server error: zone not found' for NS1 provider

Many providers make their modifications in the order that changes comes. In
python3 this causes things to be inconsistently ordered. That mostly works, but
could result in hidenbugs (e.g. Route53Provider's batching could be completely
different based on the order it sees changes.) Sorting changes consistently
is a good thing and it shouldn't hurt situations where providers are already
doing their own ordering. All-in-all more consistent is better and we have to be
explicit with python 3.

Rel 0.9.8 with a bunch of pypi readme/description fixes

v0.9.7 version bump and CHANGELOG updates

Add a Transip provider

- Added Specific exceptions
- str() instead of concatenation
- removed zone not found warning

Transip sdk also supports a private_key_file,
so forwarding that option to the provider.
Could be handy in combination with k8s secrets.

Fixes an exception in combination
with the yamlProvider as a target
The unmodified value object isn't
represented as string while
building the yaml output
The Exception:
  yaml.representer.RepresenterError:
  ('cannot represent an object', 1.1.1.1)

yaml/representer.py@249,
represent_undefined()