Actor Components incorrectly appearing mixed with the Scene Component Hierarchy in the Component Tab of the Blueprint Editor

This is a regression introduced by CL 45871568 in ue5-main branch. The new function FFBlueprintEditorDefaultSortUICustomization::SortSubobjectData() in file "BlueprintEditorSCSEditorUICustomization.cpp" uses a sort comparator that:

• correctly handles the case where A is a scene component and B is not
• does not handle the case where B is a scene component and A is not, falling back to lexicographical comparison of their DisplayNames

This results in an inconsistent (non-symmetric, non-transitive) comparator. Depending on the comparisons performed internally by the sort algorithm, an ActorComponent can be placed before a SceneComponent (even the root) if its name comes before lexicographically.

The licensee in the linked EPS case has suggested an alternative comparator.

1. On the Content Browser, create a new Blueprint Class derived from Actor.
2. Open the new blueprint
3. On the Components Tab, click "Add" and choose a non-scene Component (e.g. Rotating Movement Component)
4. Rename the new component to simply "A" (or anything that sorts before "DefaultSceneRoot" lexicographically)
5. Use Ctrl+D to duplicate the new component several times
5.1. At some point (probably around 8 components in total), the component list will get sorted incorrectly, with some non-scene components sorted before the root scene component