fix: sort root nodes unless opted out via suppressAlphabeticalSorting

[HendrikThePendric]

Implements LIBS-864

---

Description

Root nodes are now sorted alphabetically unless opted out via suppressAlphabeticalSorting. I've scoped this as a fix, because I'd say that this behaviour should have been implemented all along. Sorting children but not roots, while having a generic suppressAlphabeticalSorting prop in place is inconsistent behaviour.

Incidental

• I deduped the deps as well
• It seems an i18n string for the select was missing, it "popped up" when ran yarn setup. Not sure why it didn't get added before, but it seems like a valid addition to me.

---

Checklist

• API docs are generated N/A
• Tests were added
• Storybook demos were added N/A

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[dhis2-bot]

🚀 Deployed on https://pr-1753--dhis2-ui.netlify.app

[tomzemp]

Looks good to me @HendrikThePendric 🙏 . I've read through the code and tested in the users app (data entry app has custom org unit tree, so we'll need to copy these changes).

The only thing I noticed on review is that the existing helper function sortNodeChildrenAlphabetically is using left.displayName.localeCompare(right.displayName). I guess this then uses the sorting conventions of the browser language, whereas we might want to use the user's ui language? This can cause some differences in the sort, e.g. English would alphabetise [Åland, Belgium, Zimbabwe] whereas Norwegian would alphabetise [Belgium, Zimbabwe, Åland] (or English [na,ño,ny], vs Spanish [na,ny,ño]). I think this is a minor issue, but might be nice to fix in the context of this PR?