[Parity] Ender Pearl Stasis Chamber bugs in Bedrock (415 block desync)

Ender Pearl mechanics in Bedrock Edition are fundamentally broken and lack Java parity. The bug where pearls lose their owner link (UUID) or randomly despawn does not just break Stasis Chambers; it ruins ALL gameplay (combat, traversal, redstone). Tested and confirmed issues:

1. Distance Desync (415-445 Blocks): Moving away triggers a desync between 415 and 445 blocks. The pearl loses its owner UUID; it stays visible but fails to teleport.
2. Relog Bug: Leaving and rejoining the world permanently breaks the pearl's link or deletes it.
3. Intermittent Collision: The pearl often hits the trapdoor but fails to teleport (30%+ failure rate). Sometimes it vanishes on contact.
4. Random Despawns: Even when remaining WITHIN the 415-445 block limit, thrown pearls randomly disappear, making them highly unpredictable.
5. No Chunk Loading: Unlike Java, suspended pearls do not keep the chunk loaded.
6. Sponge Bug: Activating a chamber with a sponge deletes the pearl entirely.

Proposed Solution:

• Fix entity tracking so pearls never lose their owner UUID or randomly despawn (both within and outside the 415-445 block limit).

• Ensure the teleport event triggers 100% of the time upon collision.

• Implement Java parity for intentional chunk loading via Ender Pearls.

Ender Pearls are a core item. These desyncs make them a gamble. Fixing this fulfills the parity promise.