v0.9.5

One major change: Import paths now are properly escaped. This was originally an oversight and went unnoticed because people don't usually use backslashes in their paths. On Windows, we recommend using the verbatim string literals to avoid having to escape the path separator, e.g., import @"c:\foo.jsonnet".

Remaining changes are minor:

• Allow formatting of multiple files with a single jsonnet fmt invocation
• jsonnet fmt will now sort your imports alphabetically
• The Bazel Python build works again
• jsonnet fmt fixes code with mismatched newlines in { } and similar start/end syntax
• The Python bindings are now compatible with Python 3
• There is a VS2017 solution file
• The default -J paths were broken, now they include a proper "jsonnet" prefix. It's unlikely anyone was using them, since they were never advertised.