This PR fixes #2776. The issue was not just a simple rendering glitch, but a more fundamental issue, namely that rocket component locations (the return value of getComponentLocations() in RocketComponent) did not account for rotations of super-parents. For example, take this structure:

Pod Set 1
├─ Phantom Body Tube
│  ├─ Pod Set 2
│  │  ├─ Body Tube

Conditions:

• Pod Set 1 rotation: -90°
• Pod Set 2 rotation: -90°
• Pod Set 2 radial offset: 10 cm

With a total rotation of -180°, you would expect the 10 cm offset to cause the body tube to move 10 cm in the negative y direction. However, it was moving 10 cm in the negative z direction, because only the -90° rotation of Pod Set 2 was taken into account in the pod set instance locations.

A very extreme example with a double-nested pod set:

After this PR: