Position desync with dead players

[Einheit-101]

Describe the bug
getElementPosition() returns wrong values server side when a player is dead.

To reproduce

1. Go to editor
2. Use Jetpack, fly into the air
3. Use srun getElementPosition(me) -> Notice how your z position is pretty high
4. Kill the player
5. The player will fall to the earth (Client side Z position ~13.3)
6. Server-side getElementPosition(me) will still return the coordinate where the player died

Expected behaviour
getElementPosition() should not return the death position, it should return the current position because it can happen that a dead player moves away from his death position, for example when falling.

[Neproify]

This is because client is NOT sending sync packets when dead. That's why position on server is desynced.

mtasa-blue/Client/mods/deathmatch/logic/CNetAPI.cpp

Line 302 in a4a9fa0

if (pPlayer && !pPlayer->IsDeadOnNetwork())

The fix for that would be syncing pure sync packets even when player is dead. However I am not sure if it would not damage anything.

[PlatinMTA]

This is because client is NOT sending sync packets when dead. That's why position on server is desynced.

mtasa-blue/Client/mods/deathmatch/logic/CNetAPI.cpp

Line 302 in a4a9fa0

if (pPlayer && !pPlayer->IsDeadOnNetwork())

The fix for that would be syncing pure sync packets even when player is dead. However I am not sure if it would not damage anything.

Hope it doesn't, it would be a nice addition for something like a corpse system or whatever.