[EXILED::API] Fixing NPC PlayerId assignment

[SrLicht]

Description

Describe the changes

• Preventing that when spawning an NPC in the long term a player can have the same ID as another player.
• Adding 2 new methods of destruction.
  • LateDestroy(float) to destroy the NPC after a short delay (similar to the Unity component method).
  • DestroyAll() a static method to destroy all listed NPCs.
• Deprecating the old NCP.Spawn method because the player should never have been given the option to assign an ID.
• Creating new method with a parameter to add the NPC to the Round.IgnoredPlayers HashSet.

What is the current behavior? (You can also link to an open issue here)
Currently when creating an NPC an Id is assigned by RecyclablePlayerId and checking if it is in use, this should not be done since when creating a ReferenceHub in the Awake method this already assigns an available ID, which currently causes that we leave an ID permanently created and never destroyed leading to another player can use it and that there are 2 players with the same ID.

What is the new behavior? (if this is a feature change)

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

Other information:

Testing

I tested the changes by making every time I jumped an NPC I played a sound to check if the ReferenceHub.OnDestroy is correctly running and it was possible to use it again without another player/npc taking the same id.

ReferenceHub.OnDestroy

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentations

Submission checklist

• I have checked the project can be compiled
• I have tested my changes and it worked as expected

Patches (if there are any changes related to Harmony patches)

• I have checked no IL patching errors in the console

Other

• Still requires more testing