Bump to 0.2.0-SNAPSHOT since #162 changes some service APIs
Parsing JSON keys as keywords is now the default

Fixes #110

This behavior can be overridden by constructing a `body-params` by doing
`(body-params (default-parser-map :json-options {:key-fn nil}))`.
Update CHANGELOG with 0.2.0 deprecation messages
Update relative links in CHANGELOG.md for 0.2.0
Failing test case for #89
Content-type interceptor that doesn't inject octet-stream

Unlike Ring's content-type-response function, ours does not inject
"application/octet-stream" if no existing or URI-based MIME type can be
found. This allows the current default-content-type of "text/plain" to
crop up.
Test that stresses content-type-response not meddling
support :read-as option for message parameters in the data renderer

Using this

(msg/param :age {:read-as :data})

will cause the value collected in the Data UI to be read with the
Clojure reader. This allows one to enter arbitrary Clojure in the Data
UI without having to add the conversion code to transform functions.

For now, this should only be used for development.
Merge pull request #166 from pedestal/data-ui-read-as

support :read-as option for message parameters in the data renderer
Make it possible to explicitly declare v1 dataflow
Correct name of plaintext-body test
Merge pull request #165 from pedestal/default-content-type

Return default content type to text/plain. Fixes #89.
Merge pull request #163 from pedestal/two-oh-loose-ends

JSON changes for upcoming 0.2.0 release