Feat/#293: Naming Conventions, Improvements to AutoDiscovery, and ResourceDefinition

[jaredcnance]

Closes #293
Closes #384
Closes #402

Note: this is the first step to creating a path that allows removal of [Attr] altogether, but we're not quite there yet. For now you will be able to change models from:

[Attr("compound-name")]
public string CompoundName { get; set; }

To:

[Attr]
public string CompoundName { get; set; }

OtherChanges

• ContextGraphBuilder now allows resources to be added without specifying the resource name:

var builder = new ContextGraphBuilder();

// before
builder.AddResource<TestResource>("test-resources");

// after
builder.AddResource<TestResource>();

• ResourceDefinition contains custom filters and default sort

FEATURE

• write tests that address the requirements outlined in the issue
• fulfill the feature requirements

TODO

• Assess and identify any breaking changes
• Tests on ResourceDefinition

[wisepotato]

@jaredcnance maybe a good idea to add auto-discovery in the docs, or am i missing a page?

[jaredcnance]

@wisepotato see this: https://json-api-dotnet.github.io/JsonApiDotNetCore/usage/resource-graph.html#auto-discovery

Let me know if something is missing or if the organization could be improved.