Sprite position changes from buckling sometimes bug out when someone is jittering.

### Testmerges

#4505: 'Get Flat Icon Fixes' by Drulikar at commit 602124566b #4391: 'Hijack objectives' by morrowwolf at commit c34cb004ab #4534: '"Fixes" missing window frame icon states' by morrowwolf at commit 7cf004c46a #4535: 'Floodlight rework' by morrowwolf at commit dc54d78ea7 #4536: 'Fixes taking control of crit xenos' by morrowwolf at commit 9c7be0a948 #4522: 'refactor : divide survivor preset base on maps.' by Huffie56 at commit 56432ab028 #4502: 'Disable join as xeno buried spawns when there is a queue' by Drulikar at commit 1dc175ca21 #4516: 'makes LZ detector work while landed' by cuberound at commit b64b11a417

--------
### Description of the bug

This bug happens if you are buckled to something that changes your sprite position (IE: dropship chairs, or, most commonly, wallnests)

What happens is that if your character starts shaking (common causes include Coffee ODs, and larva growth) then your sprite can be reset to the middle of the tile, despite still being buckled. This looks very goofy with nests, especially, because it looks like the character is floating away from the nest.

### What's the difference with what should have happened?

If your buckled to something, your sprite should stay in the position where its supposed to. People should not fly out of their nests because they shake a bit.

-------
### How do we reproduce this bug?

1. Spawn into the game
2. OD yourself on coffee
4. Wait until you start jittering
3. Sit in the dropship chairs
5. At some point, the jittering resets your sprite to the center of the tile even though your still buckled
...................
1. Get a xeno to wallnest you (buckles you to the wall)
2. Get infected
3. Wait until you start jittering
4. At some point, the jittering resets your sprite to the center of the tile even though you're still buckled

///
This is very annoying and can cause new xeno players to unnest people or kill captured people

### Issue Bingo

- [X] Issue could be reproduced at least once
- [X] Issue happened in a recent (less than 7 days ago) round
- [X] Couldn't find an existing issue about this (https://github.com/cmss13-devs/cmss13/issues)