Fix collection sorting for grouped collections

[hanneskuettner]

Scope

When displaying collections (in selects, lists, system-collection and system-collections) they were only sorted by meta.sort (and the collection name for ties). When grouping selections the sort index starts at 1 again, so the collections appeared out of order with how you would expect it based on the data-model manual sorting.

What's changed:

• Introduced flattenGroupedCollections (not sure about the name, any suggestions?) to recursively flatten a list of collections that might be (deeply) grouped with the meta.group prop.
• After talking with @paescuj I moved the sorting to a single source of truth, the collections store
  • Introduced a new sortedCollections getter in addition to the original collections state, that is now used instead of collections whenever a sorted list of collections is needed. As such the collections is not modified and can be used in a backward compatible manner (also it is assigned to outside of the store, introducing the need for either a replaceCollections or the sorted getter)
• Added more getters in the collection store to ease repetitive filtering, and to use as intermediate lists in the store itself.

Potential Risks / Drawbacks

None

Review Notes / Questions

• Did I miss any access to .collections that would result in inconsistent sorting behavior?
• Is the sorting actually less confusing? Sometimes I still struggle with finding the collection easily.

---

Fixes #21658

[changeset-bot]

🦋 Changeset detected

Latest commit: 40d0ac8

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 3 packages

Name	Type
@directus/app	Patch
@directus/api	Patch
directus	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR