Update ApiClient Serializer Type to Include serialize method

Marking this as postponed as we focus on the vertical slice POC.

For 1.0 my guess is that this is what we'll need to focus on:

> Serialization could be relevant when we support non-read operations in 1.0.

Picking this one up. I'm going to first do some experimentation now that our CRUD methods exist to determine if a serializer would actually be useful. I'll then update the issue accordingly.

Archiving previous thoughts:

Starting this as a clearing ground for post MVP serializer related thoughts and will convert this to a more organized issue later.

Assumptions:
* For the POC, really what we were after is a deserialization - converting a JSON:API response into a simpler JS object.
* Serialization could be relevant when we support non-read operations in 1.0.
* Deserialization is a common issue for JSON:API responses, but less so for GraphQL.

Questions:
* Should the JSON:API client deserialize by default? Current thought is no.
* Should the serializer option be part of the base class, or the JsonApiClient Class? On the fence about this, but leaning base class.
* Should the JSON:API client ship with a serializer/deserializer? If yes, should we adopt a dependency, or should we create our own?

Libraries
* Jsona https://github.com/olosegres/jsona
* jsonapi-serializer https://github.com/SeyZ/jsonapi-serializer
* js-japi https://github.com/mathematic-inc/ts-japi (serializer only)
* deserialize-json-api https://github.com/weilandia/deserialize-json-api

Automatically closed - issue fixed for 2 weeks with no activity.