invariant (bug): inconsistent shrinked call sequence sometimes

[grandizzy]

Motivation

while testing fix for #5868 noticed that sometimes the shrinked sequence comes inverted, e.g.

        [Sequence]
                calldata=acceptOwnership(address) args=[0x5615dEB798BB3E4dFa0139dFa1b3D433Cc23b72f]
                calldata=transferOwnership(address,address) args=[0x7FA9385bE102ac3EAc297483Dd6233D62b3e1496, 0x5615dEB798BB3E4dFa0139dFa1b3D433Cc23b72f]

instead

        [Sequence]
                calldata=transferOwnership(address,address) args=[0x7FA9385bE102ac3EAc297483Dd6233D62b3e1496, 0x5615dEB798BB3E4dFa0139dFa1b3D433Cc23b72f]
                calldata=acceptOwnership(address) args=[0x5615dEB798BB3E4dFa0139dFa1b3D433Cc23b72f]

this happens when the same acceptOwnership call that breaks invariant is also performed before transferOwnership prereq, that is in a sequence of:

1. Alice calls acceptOwnership and reverts
2. Bob calls transferOwnership to Alice
3. Alice calls acceptOwnership and breaks invariant
   in this case shrinked indices are [2, 1] but we recreate call sequence as 1 and 2

Solution

Recreate new shrinked call sequence by respecting the order from shrunk call indices

[mattsse]

lgtm, ty

[DaniPopes]

this can just be map collect