Enable to force-disable pagination per relationship

[bkoelman]

In cases where the total number of resources of a certain type is high, but the number of related resources is consistently low, it becomes easier for clients to build master/detail views when they don't need to consider nested pagination.

For example, the total number of products in a web shop is typically high, but the number of products in a shopping basket is typically low. This PR enables turning off pagination for that relationship (while leaving the default page size activated):

public class Product : Identifiable<long>
{
    // ...
}

public class ShoppingBasket : Identifiable<Guid>
{
    // ...

    [HasMany(DisablePagination = true)] // <-- DisablePagination is new
    public ISet<Product> Products { get; set; } = new HashSet<Product>();
}

The effect is that pagination on products will be disabled for the following requests:

• /shoppingBaskets?include=products
• /shoppingBaskets/1?include=products
• /shoppingBaskets/1/products
• /shoppingBaskets/1/products?page[size]=25

Additionally, when pagination is set from a resource definition, it does not get applied. This is because resource definitions operate on resource types. The new property on a relationship overrules that, similar to how setting links on a relationship overrules the links defined on a resource type.

Caution

Only use this property when the set of related resources is known to be small. Take into account the full size of any nested includes.

For example, when the default page size is 50 and each basket contains 125 products, and each product contains 80 discount rules, the request /shoppingBaskets?include=products.discountRules returns a total of 50 (baskets) * 125 (products) * 50 (rules) = 312,500 resources!

Fixes #1731.

QUALITY CHECKLIST

• Changes implemented in code
• Complies with our contributing guidelines
• Adapted tests
• Documentation updated

[codecov]

Codecov Report

❌ Patch coverage is 85.00000% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 90.87%. Comparing base (f4980c3) to head (913248e).
⚠️ Report is 1 commits behind head on master.

Files with missing lines	Patch %	Lines
...piDotNetCore/Queries/Expressions/SortExpression.cs	62.50%	1 Missing and 2 partials ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1750      +/-   ##
==========================================
- Coverage   90.87%   90.87%   -0.01%     
==========================================
  Files         475      475              
  Lines       14690    14703      +13     
  Branches     2319     2324       +5     
==========================================
+ Hits        13350    13361      +11     
- Misses        911      912       +1     
- Partials      429      430       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.