feat: implement direct testing of score/impact of constraints

[PatrickDiallo23]

This PR is introducing the capability to get the score/impact of the constraints given a set of entities or an entire solution addressing the #2007 .

Even though it was proposed to add in ConstraintVerifier the getScore and getImpact methods, I observed that it was counterintuitive for the user to use such methods because it would change the chaining method (also making the implementation more complex than it should be) to constraintVerifier.getScore().forConstraint(constraint).given(entities).

I was thinking of providing a new chaining to obtain the score like constraintVerifier.evaluate(constraint).given(entities).score(), where evaluate() would be the same as verifyThat() resulting in duplicated code which is not a good idea.

So I used the solution provided by the author of the issue, which is the most efficient and straightforward solution that allows writing custom assertions to compare different solutions or subsets of solutions.

[triceo]

I agree that the solution presented here is the better of the proposals.

Let's mention this feature in the docs where we talk about constraint testing - I envision a new subsection, something to the tune to "Employing custom assertions", showing how to use this feature with AssertJ. (Much like the Javadoc snippets already do.)

[triceo]

Thanks, @PatrickDiallo23!

[sonarqubecloud]

Quality Gate passed

Issues
5 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud