Static Object Context for Ahead of Time compiling and Trimmed libraries

[EdwardCooke]

Includes a source generator/analyzer that generate a static type inspector and object factory. These static objects allow the creation of objects and setting/getting of object properties and fields so YamlDotNet serializer will work with trimmed libraries and ahead of time compilation because it removes the use of reflection when these static objects are used during serialization and deserialization.

Currently it has the following requirements, support and limitations:

• All objects in the YAML object graph must be annotated with the YamlSerializable attribute
• YamlIgnore and YamlMember attributes are supported and respected
• Dictionary<,> and List<> property/field types are supported.
• There is a helper method on the SerializerBuilder and DeserializerBuilder that will configure the serializer and deserializer to not use the reflection based objects and instead use the static ones.
• Arrays are supported
• Type overrides are not tested, if you annotate the real class with YamlSerializable it might work

This PR will not create or push an analyzer package to NuGet. That will come later.

This is to support creating an analyzer package manually that can be tested by the users in #740 and #753.

@aaubry , I know you are trying to take a more passive role in YamlDotNet, but I would really appreciate a review of this and the subsequent PR, at a potentially near future date, where we push up the official analyzer so people can use it for real.

[aaubry]

This feature has been released in version 12.3.0.