Allow different order in collections

[fflaten]

Checklist

• Feature request has a meaningful title
• I have searched the existing issues. See all issues
• I have tested using the latest version of Pester. See Installation and update guide.

Summary of the feature request

Should assertions like Should-ContainCollection have an option to ignore item order? Sometimes the returned order can not be guaranteed, especially in integration tests.

This is especially visible when migrating from Should -BeIn which checked individual items in the expected collection.

'a',2,$null | Should -BeIn 'b',3,2,'a',$null
# pass

'b',3,2,'a',$null | Should-ContainCollection 'a',2,$null
Expected [Object[]] @('a', 2, $null) to be present in [Object[]] @('b', 3, 2, 'a', $null), but it was not there.

'b',3,2,'a',$null | Sort-Object | Should-ContainCollection ('a',2,$null | Sort-Object)
# pass but ugly

How should it work?

-IgnoreOrder parameter?
Or close request and let this issue document the required use of Sort-Object.

[nohwnd]

There is definitely room for adding parameters to the assertions, that is one of the reasons we have them separate. I was not sure if the default checking in order was correct, and probably we should choose a direction, to decide if it should go strict (default) -> less strict, or the otherway around, and what is the convenience price for that.

Probalby worth asking copilot to look at all our new assertions and figure out the pattern.