Remove an order dependency in LabelsFinder specs

What does this MR do?

Makes the LabelsFinder spec expectations order-independent

Are there points in the code the reviewer needs to double check?

There is an explicit ordering to LabelsFinder - title ascending - but two of the labels (a group label and a project label) have the same title, so the sort ordering isn't stable for those in all circumstances. It looks like this is intentional.

Why was this MR needed?

Tests failing on at least Debian CI: https://ci.debian.net/data/packages/unstable/amd64/g/gitlab/latest-autopkgtest/log.gz

Does this MR meet the acceptance criteria?

• Tests
  • Added for this feature/bug
  • All builds are passing
• Conform by the style guides
• Branch has no merge conflicts with master (if it does - rebase it please)
• Squashed related commits together