V14: Add reserved fields to config endpoints

[Zeegaan]

Notes

• Added configuration endpoint for members
• Added new ConfigurationPresentationFactory, that is responsible for creating the configuration models
• Added new IReservedNamesService that will return all the reserved names for a given model (Member, Media, Content)
• Added 3 new property settings, so that users (or package devs) can define their own reserved names.

How to test

• Using the 3 configuration endpoint, assert that you get the correct list of reserved names
• Try configuring the property settings & add some reserved names yourself, assert these also get returned via the endpoints
• You can use this code to configure the property settings:

public class TestComposer : IComposer
{
    public void Compose(IUmbracoBuilder builder) =>
        builder.Services.Configure<ContentPropertySettings>(
            x =>
            {
                x.AddReservedFieldName("myReservedFieldName");
                x.AddReservedFieldName("anotherOne");
            });
}

[elit0451]

LGTM 💪

[nikcio]

Hey @Zeegaan

I just stumbled across the ReservedFieldNamesService.cs and found it a bit weird that it's placed as part of the Umbraco.PublishedCache.NuCache as it doesn't seem to be needed in a caching context. I can see the only dependency that isn't available outside Umbraco.PublishedCache.NuCache in the file is PublishedMember so maybe an interface should be created instead so the service doesn't have a hard link to the internal cache implementation.

Just a thought 😄

[Zeegaan]

@nikcio There is a reason that we have left the implementation in the NuCache project, this is because the PublishedMember is internal and is at the moment, and is only available in this project 😢
At some point, we could probably move it, by making PublishedMember public or refactoring it in some way, but that was too big of a scope creep at this point 🙈