Errors in logs when adding and removing modules

[SpaceMonkeyy86]

Describe the issue

• Join a world with two players
• Spawn a seamoth or exosuit, then try to add or remove upgrades or arms

[16:42:34.924] [ERR-UNITY] Unregistering id 'd101f923-5850-4d02-af34-497d3203daa6' (class 'cfea2a50-6fc1-41f7-b496-a36a31b0639f', registered class 'cfea2a50-6fc1-41f7-b496-a36a31b0639f') failed because it already changed to 'ExosuitDrillArmModule(Clone)' at (39.2, -14.8, -283.2), used to be 'ExosuitDrillArmModule(Clone)' at (38.2, -12.1, -283.3)
[16:42:35.825] [ERR-UNITY] Unregistering id '2d7a8a1c-872c-49da-949f-00bba9e0a7cf' (class 'ce9e25f2-b062-4c3d-bf10-abc1f08ad2f7', registered class 'ce9e25f2-b062-4c3d-bf10-abc1f08ad2f7') failed because it already changed to 'ExosuitGrapplingArmModule(Clone)' at (39.2, -14.8, -283.2), used to be 'ExosuitGrapplingArmModule(Clone)' at (38.2, -12.1, -283.3)
[16:43:24.886] [DBG] Received: Added item ExosuitDrillArmModule (d101f923-5850-4d02-af34-497d3203daa6) to container Landscape/Global Root/Exosuit(Clone)
[16:43:24.893] [ERR-UNITY] Unregistering id 'd101f923-5850-4d02-af34-497d3203daa6' (class 'cfea2a50-6fc1-41f7-b496-a36a31b0639f', registered class 'cfea2a50-6fc1-41f7-b496-a36a31b0639f') failed because it already changed to 'ExosuitDrillArmModule(Clone)' at (37.6, -12.5, -283.6), used to be 'ExosuitDrillArmModule(Clone)' at (39.2, -14.8, -283.2)
[16:43:25.264] [DBG] Received: Added item ExosuitGrapplingArmModule (2d7a8a1c-872c-49da-949f-00bba9e0a7cf) to container Landscape/Global Root/Exosuit(Clone)
[16:43:25.268] [ERR-UNITY] Unregistering id '2d7a8a1c-872c-49da-949f-00bba9e0a7cf' (class 'ce9e25f2-b062-4c3d-bf10-abc1f08ad2f7', registered class 'ce9e25f2-b062-4c3d-bf10-abc1f08ad2f7') failed because it already changed to 'ExosuitGrapplingArmModule(Clone)' at (37.6, -12.5, -283.6), used to be 'ExosuitGrapplingArmModule(Clone)' at (39.2, -14.8, -283.2)

^ Added a drill arm and grappling arm to an exosuit, then removed them in that order

Additionally, Equipment_RemoveItemPatch appears to incorrectly set the new parent id of the item to the id of the former parent, which could cause problems with nuclear reactors or cyclops decoy loading tubes (untested).

These errors don't cause any user-facing issues, but they might lead to problems in the future.