[TF2] fix caber explosion not being lag-compensated

[wgetJane]

Description

fixes ValveSoftware/Source-1-Games/issues/7761

unfixed, minimum interp time:

caber_15interp_unfixed.mp4

unfixed, default interp time:

caber_100interp_unfixed.mp4

fixed, default interp time:

caber_100interp_fixed.mp4

[wgetJane]

minor note: this could potentially not unlag all players that the explosion should reach because of the WantsLagCompensationOnEntity filter:

source-sdk-2013/src/game/server/tf/tf_player.cpp

Line 20078 in 7191ecc

bool CTFPlayer::WantsLagCompensationOnEntity( const CBasePlayer *pPlayer, const CUserCmd *pCmd, const CBitVec<MAX_EDICTS> *pEntityTransmitBits ) const

the filter includes players that are within a 45 degree cone from the attacker's crosshair, and players that are within a certain distance based on the attacker's max walk speed and the value of the sv_maxunlag cvar:

source-sdk-2013/src/game/server/tf/tf_player.cpp

Lines 20128 to 20130 in 7191ecc

	// get max distance player could have moved within max lag compensation time,
	// multiply by 1.5 to to avoid "dead zones" (sqrt(2) would be the exact value)
	float maxDistance = 1.5 * pPlayer->MaxSpeed() * sv_maxunlag.GetFloat();

sv_maxunlag's default value is 1.0 and the caber user's walk speed is going to be 280 unit/s (or 308 with booties)

so under normal circumstances this distance is going to be 420 units (or 462 with booties), which is well above the caber explosion's radius of 100 units

if the caber user's max walk speed is somehow set really low (maybe through vscript idk) or sv_maxunlag is set to a very low value (i think older anticheat plugins do this), then the distance might not be enough to reach every player that should be lagcomped

though again, this is really minor, just something funny to note
(maybe weapons should have a WantsLagCompensationOnEntity method? probably out of scope for this pr though)