Movements overhaul

[tornac1234]

Reason for PR 🤔:

Current state of vehicles movements is really poor, both for regular play, and for testing the brand new #2106.
+ the network optimization behind movements is currently really poor and mostly random
Latest rework of movements (after modpocalypse) messed up movements sync, and it was never that suitable for Nitrox.

Benefits of the PR 🤩:

Will drastically improve movements for players and vehicles:

• Only 30 packets/second are now required per tracked unit (players and vehicles) which is a lot better than it used to be (it had even poorer visible performance)
• Packets will be lighter than before
• New system is adaptable to poorer connections (there are two settings for the automatically adjusted latency system)
• While having different latency between players might cause a bit of frustration (e.g being hit on another player screen while they're still safe on their own screen), it is the best compromise between performance and playability.

Tasks for myself 🍙🍜🍣 (I kept the best ones 😋):

• Reimplement channels in LiteNetLib (we always had a setting in packets but we never actually fed it to LiteNetLib)
• Create a new dedicated MovementReplicator MonoBehaviour responsible for reproducing players and vehicles movements, while automatically taking variable latency into account
• Deprecate our old system (delete the old packets and MultiplayerCyclops (etc) behaviours)
• Make some classes inheriting from MovementReplicator for the Cyclops, Seamoth and Exosuit to have their animations working accordingly with the replicated movement.
• Have players be set to at the right position when they're driving a vehicle (vehicles packets' might require at least one more field or two for steering wheel and throttle data (can probably be reduced to a byte for the angles, and a bool for appliedThrottle), but as long as we know it's a cyclops, we can hardcode the relative localposition to avoid sending that data

Tasks assigned to @Jannify 🍕🍔🍟 (thanks for proposing your help 😀):

• Finally make use of VehicleOnPilotModeChanged packet to be the trigger of a remote player entering/exitting a vehicle (and no longer have a very weird logic like the current Vehicles.UpdateVehiclePosition)
• Ensure remote players remain in place during the driving (that I supposedly fixed with cyclops movement PR)
• Rework docking and undocking accordingly to the new movement system (a trigger must be sent to start the animations, during which remote players will ignore incoming data for the vehicles involved)

Translations to be added to Weblate 📜🌐:

• NitroxBandwidthSettings: Bandwidth Settings
• NitroxHigherForUnstable_Tooltip: Give a higher value for more unstable connections
• NitroxSettingsLatencyUpdatePeriod: Latency Update Period (s)
• NitroxSettingsSafetyLatencyMargin: Safety Latency Margin (ms)

Context images for the translations:

[tornac1234]

This PR is now ready for both tests and reviews :)