Joint orders does not always match tree hierarchy

[htp2]

Hi Adnan, as discussed, there is at least one example of the plugin generating the joints (and bodies) in the ADF file in an order that does not match the parent/child hierarchy. So if bodies A,B,C,D are connected by joints 1,2,3 by A-1-B-2-C-3-D, you would expect bodies to be listed "A B C D" and joints "1 2 3", but they can appear out of order.

This can cause an issue when using the ambf python client as most users will assume the joint order matches and will see unexpected behavior.