Introduce a version of the SelfReferencingCollectionAssertions.SatisfyRespecitvely method which is not sensitive to the order of elements and accepts predicate expressions.

Example of an assertion:

plannedOrders.Should().Satisfy(
    order => order.Type == OrderType.Purchase && order.Quantity == 5 && order.Date == tomorrow,
    order => order.Type == OrderType.Transfer && order.SourceLocation == distributionCenter && order.Quantity == 3 && order.Date == today,
    order => order.Type == OrderType.Transfer && order.SourceLocation == factory && order.Quantity == 5 && order.Date == today.AddDays(10)
);

Example of a failure message:

Expected collection to satisfy all predicates because we want to test formatting (args), but:
    
    The following predicates did not have matching elements:
    
    (_.Text == "two") AndAlso (_.Number == 2)
    
    The following elements did not match any predicate:
    
    FluentAssertions.Specs.Collections.GenericCollectionAssertionsSpecs+SomeClass
    {
       Number = 1
       Text = "one"
    }
    
    FluentAssertions.Specs.Collections.GenericCollectionAssertionsSpecs+SomeClass
    {
       Number = 3
       Text = "two"
    }
    
    FluentAssertions.Specs.Collections.GenericCollectionAssertionsSpecs+SomeClass
    {
       Number = 3
       Text = "three"
    }

The discussion about this API is tracked here:
#1480

To enable the necessary functionality three major changes were introduced:

• The Satisfy API was added to the SelfReferencingCollectionAssertions class.
• The MaximumMatchingSolver class was added to encapsulate the simplified version of the Ford-Fulkerson algorithm to find matching between the asserted predicates and the elements of the collection.
• The PredicateLambdaExpressionValueFormatter class was introduced to produce more human-readable descriptions of predicates in assertion failure messages.

IMPORTANT

• The code complies with the Coding Guidelines for C#.
• The changes are covered by a new or existing set of unit tests which follow the Arrange-Act-Assert syntax such as is used in this example.
• If the contribution adds a feature or fixes a bug, please update the release notes, which are published on the website.
• If the contribution changes the public API the changes needs to be included by running AcceptApiChanges.ps1/AcceptApiChanges.sh.
• If the contribution affects the documentation, please include your changes in this pull request so the documentation will appear on the website.