`Deserializer` flattening makes `data.attributes.type` collide with `data.type`

[grzuy]

Hi there,

Flagging a minor limitation we found when using the Deserializer plug.

If one is accepting data for creating a resources that has an attribute named type, the deserializer would make the attribute override/collide with the resource type in the resulting map.

It might not be very common issue to anyone, but just wanted to document it.

Workaround I guess is to just not expose the attribute as type and use a different name.

Cheers.