Added custom contract resolvers to handle STJ property name attributes

[markphillips100]

This PR fixes #113 by adding 2 new Json.Net contract resolvers to replace usage of existing DefaultContractResolver and CamelCasePropertyNamesContractResolver implementations. Their primary purpose being to retain the existing camel casing behaviour or not as required, with support for deserializing property names where the property is using a System.Text.Json.Serialization.JsonPropertyNameAttribute.

Some notes:

1. Added some unit tests to validate the behaviour.
2. Did not change the base type of PropertyIgnoreSerializerContractResolver as was unsure of the impact.
3. Modified all ContractResolver assignments to use the appropriate new resolvers.
4. There appears to be a broken unit test unrelated to this change, notably ValidateDateTimeFormatForDefaultDateTimeString().
5. Added an msbuild property to build\AssemblyVersion.proj to allow me to not include my username in version. My local username ends in an underscore (no idea why) and this caused a problem building.

[markphillips100]

@microsoft-github-policy-service agree [company="default"]

[markphillips100]

@microsoft-github-policy-service agree

[hsubramanianaks]

@markphillips100 Thank you for the PR. I appreciate it.
ValidateDateTimeFormatForDefaultDateTimeString - this UT is not failing in our CI/CD pipelines, and I manually tested them in my local which doesn't fail either. It Should be something related to your local machine.
we will review your changes further and let you know.

Thanks,
Hari

[markphillips100]

@hsubramanianaks out of curiosity, are you (and your devops pipelines) in the UK? I'm east coast Australia and for my local windows 11 tests the DateTime.Parse(dateTimeString) used in the test will result in a local datetime which does not compare to the default(DateTime) used in the extension method under test.

If I convert the parsed datetime to universal time then the extension works as intended:

[Fact]
public void ValidateDateTimeFormatForDefaultDateTimeStringWhenPassedUtcKind()
{
   var dateTimeString = default(DateTime).ToUniversalTime().ToString("s") + "Z";
   Assert.Equal("-", DateTimeExtensions.FormatDateTimeUtcAsAgoString(DateTime.Parse(dateTimeString).ToUniversalTime()));
}

[markphillips100]

Is someone else going to merge the latest changes? Also, any chance this can be reviewed and released soon?

[elenavillamil]

Hi! Thank you very much for your PR. I have left some small comments. The main changes look good!

[elenavillamil]

Is someone else going to merge the latest changes? Also, any chance this can be reviewed and released soon?

Hi @markphillips100, sorry for the delay we were focused on the switch to dotnet6. We have had some time in the past couple days to look at this PR and once we get green light from our testing team Monday we should be able to merge it. If you can remove the launchSettings.json file it would be ideal, but it is not a big issue if it stays.