Why are we making this change?

One of cynics features is that it allows you to use types from any crate as custom scalars, bypassing the usual orphan rule restrictions. In other words, cynic doesn't have to specifically add support for that crate, and that crate doesn't need to add support for cynic either.

Currently this uses the serde::Serialize & serde::Deserialize impls for the type. This is fine when the format used by the serde impls matches that used by the server you're talking to. But when the format does not match, you can no longer use the type directly, and have to create a wrapping newtype instead.

What effects does this change have?

This PR updates the cynic code so that it uses a set of cynic traits for serialising & deserialising scalars. These types are generic over the underlying schema type - allowing the ser/de of scalars to hook into the same schema specific mechanisms we do to match types to custom scalars.

This means that an application can serialise one individual type differently depending on what the server it's sending to expects.

Fixes #782

Todo:

• There's at least one todo!() in there.
• There's some commented out code that needs fixed
• More thorough tests of flatten to make sure I've not broken it
• Doc updates
• Write tests of this functionality.
• Figure out if I need more where bounds on some of the generated impls