Sync persistent projectiles (satchels, teargas, molotov) on stream-in

[TheCrazy17]

Summary

Sync persistent projectiles (satchels, teargas, molotov) to players who stream in or join after the projectile was created.

Previously, if a satchel charge was thrown while a player was out of range (or not yet connected), no projectile was ever sent to them; it simply didn't exist on their client. This PR introduces three mechanisms to fix that:

1. Stream-in resync (ProcessProjectileStreamIn): The server tracks a list of persistent projectiles per-player and periodically sends their creation packet to any nearby player who hasn't been notified yet.
2. Rest-position packet (PACKET_ID_PROJECTILE_REST_POSITION): Once a satchel settles, the owning client reports its actual resting position and attach offset to the server. Future stream-ins place the satchel directly at that spot instead of replaying the original throw and re-simulating physics (which is non-deterministic).
3. Pending creation queue (client-side): If a projectile packet arrives before the creator's game entity has streamed in, the creation is queued and retried for up to 60 seconds instead of being silently dropped.

Motivation

Persistent projectiles (satchels in particular) have never been synced to late-joining or streaming-in players. A satchel planted by a player was invisible to anyone not already in range when it was thrown — detonating it would produce an explosion out of thin air on those clients.

Two edge cases drove most of the design:

• Attached satchels: if the satchel stuck to a moving vehicle, replaying the original throw would leave it at the wrong world position. The rest-position packet carries GTA's own native attach offset so the resync re-attaches it at the exact same point on the entity.
• Collision not loaded: when a satchel is placed via resync (zero force/velocity), local collision geometry may not be streamed in yet, so SetStaticWaitingForCollision prevents it from falling through the world.

Fixes #369 / #368 (duplicated).

Test plan

Satchel visible to late-joining player

1. Player A throws a satchel and lets it settle.
2. Player B connects / streams into range after it has settled.
3. ✅ The satchel appears on Player B's screen at the correct resting position (no throw animation replayed).
4. Player A detonates ✅ explosion is at the same spot on both clients.

Satchel attached to a moving vehicle

1. Player A throws a satchel that sticks to a vehicle. The vehicle moves away.
2. Player B streams in.
3. ✅ The satchel appears attached to the vehicle at the correct offset (e.g. the hood), not at the vehicle's origin and not left at the original world position.

Teargas / Molotov visible to streaming-in player

1. Player A throws a teargas grenade or molotov.
2. Player B streams into range while the effect is still active.
3. ✅ The effect is visible on Player B's screen and disappears after its normal lifetime (~20 s).

Creator not yet streamed in

1. Player A (out of view) throws a satchel, then walks toward Player B.
2. ✅ As Player A's entity streams in, the satchel is created correctly and not silently dropped.

Checklist

• Your code should follow the coding guidelines.
• Smaller pull requests are easier to review. If your pull request is beefy, your pull request should be reviewable commit-by-commit.