Honour DataMember and DataContract attributes

[russcam]

This commit updates the behaviour of TypeNameResolver and
PropertyMapping to respect the usage of DataMember and
DataContract attributes for all requests.

Prior behaviour to this commit was that indexing would honour
DataMember attributes on a document due to the internal implementation of
JSON.Net honouring them. With other requests such as Search however,
where a Field type is used, the the resolution of the Field string name did
not honour the attributes.

Closes #3107

[codebrain]

• Update docs with resolve ordering information
• Split test into type name / property name

LGTM though.

[D9001]

I'm using .NET Core 2.2 with NEST 7.0.1, and whenever I have a class with DataContract and DataMember on a nested property, the objects in the nested property array are created as [{},{}] (if I have 3 properties, there would be 3 empty objects inside). When I take DataContract and DataMember attributes off, everything is serialized just fine.. Is this a known issue?

Is there any way around this? I'd like to avoid creating extra classes with the same properties but different attributes.

[russcam]

@D9001 It's best to open a separate issue about this and link to this PR; a comment is likely to end up being lost as it's not as visible as an issue. Please open an issue an provide as much detail as you can, ideally with a reproducible example, so that it helps understand more quickly.

[niemyjski]

We have our own json.net serializer defined in NEST 7.5.1 and we are doing our own naming strategy that ignores DataMember Attributes (on purpose) and we are hitting our break points as expected. But we noticed that the models that are being serialized that have the data member name are preserved even though our naming strategy is hit.. Any idea why this would be happening in NEST 7, was working as expected in NEST 5.