Add SerializedNameConvention annotation and metadata

[anonymous123-code]

Metadata types can be made inhertitable by using true in the create methods (There are overloads defaulting to false) When the config builder is finally built, all inheritable metadata is propagated and applied to its children. If children specify their own metadata, that takes precedence.

Additionally makes it so that ConfigFieldAnnotationProcessors can also process the config class's annotations.

Specific to SerializedNameConvention

• it is inherited
• Adds a serialized naming scheme annotation, allowing for automatic case conversion for serialization
• The NamingScheme interface and the NamingSchemes enum, inspired by Configurate, but more flexible to prepare for #30
• Both NameConvention.custom() and NameConvention.value() can be set at the same time, but NameConvention.custom() takes priority.
• Sections inherit the main config class's NameConvention by default.
• Sections can have different NameConventions for their nested values. A NameConvention annotation to the section field, with the annotation on the field taking priority.
• The default naming scheme is PASSTHROUGH, for backwards compatibility.

Based on #4 Fixes #29

[ix0rai]

please run applyLicenses!

[anonymous123-code]

Should the metadata when applied using the builder also be inherited? I think so and then a new API for inherited metadata might be a good idea.

[ix0rai]

@anonymous123-code I'm not sure what you mean by that, can you elaborate?

[anonymous123-code]

Currently, only the annotations are propagated to children (A annotated config will set defaults for all properties and sections it contains etc.), but if I add metadata using the builder that is not propagated. This means that only the ReflectiveConfig can use that shortcut. I think it would be better if there was a type of metadata that gets propagated to children, even if added through the builder. This would imply some new API stuff and widen the scope of this PR

[ix0rai]

@anonymous123-code any plans to finish this?

[anonymous123-code]

This is now ready for review again. Quite a lot of stuff changed; and I updated the PR description