fix(es_extended/client/main): fix player death race condition

[Kenshiin13]

Description

The current spawn event flow for multicharacter is structured as follows:

1. The player loads into the server, triggering the playerSpawned event during multichar setup.
2. On character selection, the following events are triggered in this order:
   1. esx:playerLoaded
   2. playerSpawned
   3. esx:onPlayerSpawn
   4. playerSpawned (Redundant and removed by this PR)

This PR addresses two key issues:

1. Redundant playerSpawned Trigger
   The playerSpawned event was redundantly triggered in the ESX.SpawnPlayer function callback, even though the function itself already triggers this event. This PR eliminates the unnecessary duplication.

2. Health & Armor Metadata Race Condition
   Player metadata, such as health and armor, is now applied within the esx:onPlayerSpawn event instead of esx:playerLoaded. This resolves the following issue:

   • The player's health, which could be set to 0 (causing death), was being applied before their death state was reset in esx:onPlayerSpawn. This created a race condition where a player might be killed during esx:playerLoaded and then have their death state reset immediately afterward in esx:onPlayerSpawn.

Additionally, while not explicitly targeted, this PR also appears to fix a related issue where the death screen in esx_ambulancejob would fail to display after combat logging. Since esx:onPlayerSpawn is used by esx_ambulancejob to remove the death screen (the same event where metadata is applied and the player could potentially die), this change indirectly resolves that behavior.

To fully address this issue, I will submit a separate PR to esx_ambulancejob to ensure the death screen logic ignores the first spawn event. This should eliminate any remaining race conditions in the handling of player states. This logic has been fragile for some time, and this PR is a step towards stabilizing it.