containExactlyInAnyOrder does not handle custom verifier properly about kotest

[Kantis]

I think we should deprecate the method accepting the custom verifier. I think it's a bit problematic in this method.. My reasoning is as follows..

Given a custom verifier, there's no guarantees that the equality implementation is associative. Normally A == B and B == C implies that A == C. That might not be the case depending on how a user implements their verifier. This becomes a problem when implementing containsExactlyInAnyOrder.

When associativity applies, we can simply find any match to an element and it's equally fine to "consume" that match and move on and check if the rest of the elements manage to find a match. If all elements find a match, the assertion is a success.

Without associativity, we need to test every permutation of pairing the elements of the lists, otherwise we might end up with a false negative assertion.

[Kantis]

Just noticed that this duplicates #3820 and a PR to fix it in #3821.. Will review that and contemplate for a bit.