Fix - topological sort, - key not matching internally.

[KevinJump]

Fixes an issue where the sort order for the import of doctypes was wrong.

When we introduced routes we updated the key used in the OrderedNodeInfo class to include the local path, so it would be unique between folders - except it doesn't have to be anymore

the knock on effect of this was the OrderedNode had a unique key which was then different from the internal Key value on the XML element.

the key on the XML element was the one being added to the GraphEdge classes which go in to doing the sort (based on composition dependencies). but because the node and edge keys where coming from diffrent places we never ended up with the correct match so the topolgical sort would fail and the level sort becomes the default.

this is less then ideal for compoitions as they are often deeper down the tree than the content pages that use them. so this can cause issues with imports (especially on shared tabs).

turns out v13 tollorates this (e.g it doesn't mind if you create the property in a tab before you have actually created the tab in dependent content type). but v15+ does not :( .

this fixes that

[Copilot]

Pull Request Overview

This PR fixes a topological sorting issue in the uSync.BackOffice where the key used in OrderedNodeInfo wasn't matching the key used internally for XML elements, causing import order problems.

• Simplifies the key generation in OrderedNodeInfo to use the node's native key directly
• Removes the composite key format that included local path information
• Ensures consistency between node keys and graph edge keys for proper topological sorting

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}