undo sorting in buildDomain()

[bhalsey]

Issue:

• https://linear.app/fusionauth/issue/ENG-2184/client-code-generation-is-non-deterministic

Problem:

Previous PR that sorted domain objects introduced extraneous imports (using) in the netcore client. This is from the sorting that was also added to the buildDomain() function. Turns out the sorting in buildClient() is the only one needed to make the go client and typescript client generation stable.

Solution:

Remove the extraneous sorting that introduces issues. Added comment about clobbering that happens with type to package name mapping.

Linked PR:

• sort domain objects by class name #3

Reviewer Notes:

The netcore client generation freemarker has a fair bit of handcrafted logic in it to work. Perhaps this can be refactored, but I didn't want to go down this rabbit hole. Part of the issue is that we reuse names for static inner classes like LambdaConfiguration