ghost EHandle

[AdamTadeusz]

Description

There is a rare issue that's come up a few times where the ghost marker gets placed on objects which are not the ghost. This PR aims to hopefully solve this issue by creating a networked chandle for the ghost object, and using that instead client side to get the ghost position. This PR also makes the position of the ghost marker when carried by players behave more like in the original

Toolchain

• Windows MSVC VS2022
• Linux GCC Distro Native [Specify distro + GCC version]
• Linux GCC 10 Sniper 3.0

Linked Issues

• fixes #

[AdamTadeusz]

I didn't know if we should keep m_vecGhostMarkerPos, decided to keep it as a fallback instead of returning vec3_origin.

[DESTROYGIRL]

Could this change also be applied to the juggernaut, as the HUD logic was copied from the ghost?
You should only need to make a handle for the juggernaut item as thats the only thing the marker appears on. But the marker position vector might need to stay as thats used between the juggernaut item and juggernaut player for the compass arrow

[AdamTadeusz]

I wanted to but I didn't feel confident doing it since it was behaving a little differently that the ghost so I undid those changes

[sunzenshen]

Seems to work better now with mp_restartgame 1 (didn't run into the ghost marker following a player bug)