[TF2] Fix prediction for force-a-nature jumps

[wgetJane]

fixes this issue partially: https://github.com/ValveSoftware/source-1-games/issues/6017

unfixed, net_fakelag 100:

https://github.com/user-attachments/assets/10c4b937-72a5-4c46-b198-43318ac1546a

fixed, net_fakelag 100:

https://github.com/user-attachments/assets/7f37d57e-bdf0-4411-b3a2-6cd2004947eb

CAVEAT: this does not fix prediction for the "stun" that gets self-applied by FaN-jumping, which reduces your airstrafing control

i feel like it's a separate issue to fix, though i would personally just remove the self-stun since it seems pretty odd to have in the first place, but that can be easily interpreted as a balance change

this still makes FaN jumps feel a LOT smoother, but the screen jitter would still happen if you try to airstrafe immediately upon a FaN jump at high ping

btw i also tested this in other people's random frog fortress servers, so this works completely clientside as well

[FlaminSarge]

Heads up, I was planning on opening a PR for https://github.com/mastercomfig/tf2-patches-old/pull/462

Should I pull in these changes into that as well for the sake of Valve (and community projects) being able to pick up both changes easily without messy rebase/merge?

[wgetJane]

sounds good, though i'll keep this pr open until yours is sure to be merged

maybe if possible, pull my commit from this pr first for your pr so it's less potentially messy

[misyltoad]

Had to merge manually, but ty

[FlaminSarge]

(For bookkeeping: https://github.com/ValveSoftware/source-sdk-2013/commit/a62efecf624923d3bacc67b8ee4b7f8a9855abfd )