feat(es_extended/client/modules/death): add gameEventTriggered for pl…

[foltone]

feat(es_extended/client/modules/death): add gameEventTriggered for player death handling

---

Description

This merge request implements the gameEventTriggered event to handle player deaths. The logic distinguishes between deaths caused by another player (Death:ByPlayer) and natural causes (Death:Natural), ensuring code robustness and optimization.

---

Key Changes

• Implemented gameEventTriggered to manage CEventNetworkEntityDamage for player death detection.
• Added the following functions:
  • Death:ByPlayer: Handles deaths caused by other players.
  • Death:Natural: Handles deaths from natural causes.
  • Death:ResetValues: Resets death-related data after processing.
• Improved client-server event communication with esx:onPlayerDeath.

---

Checklist

• My PR title and commit messages follow the Conventional Commits standard.
• My changes have been tested locally and work as expected.
• My PR does not introduce breaking changes.
• I have provided a clear explanation and context for the changes.

---

Rationale

• Fixes gaps in the player death handling system.
• Improves robustness and entity validation checks.
• Ensures better communication for client and server death events.

Thank you for reviewing this PR and helping improve death handling in ESX! 🎉

[Kenshiin13]

This was the previous method we used for the death module and has been replaced by a simple thread. CEventNetworkEntityDamage is very much overkill as it can be triggered hundereds of times per second when driving a vehicle into an object for example. There is no plan for us to switch back, the current thread works just fine.