Fix CombatTracker stale on death

[Doc94]

Fix #12558 where player replace the combattracker on death, this PR make the PaperCombatTrackerWrapper part of the NMS CombatTracker for avoid stale instances.

[Doc94]

not sure also if maybe is better just make the get in the Craft clalss build the wrapper every time for avoid this edge case. but the fixs works.

[lynxplay]

Yea I think recreating the instance is a fine alternative.
The current behaviour is gonna run into issues once we (finally) stop reusing the ServerPlayer instance and would need to be re-migrated.

Alternatively, the nms CombatTracker could hold its own API view (similar to Entity's getBukkitEntity) and we return that.
A single record creation there should really not be a big deal tho, no state is copied in the creation, all methods are stateless.

[Doc94]

Yea I think recreating the instance is a fine alternative.
The current behaviour is gonna run into issues once we (finally) stop reusing the ServerPlayer instance and would need to be re-migrated.

Alternatively, the nms CombatTracker could hold its own API view (similar to Entity's getBukkitEntity) and we return that.
A single record creation there should really not be a big deal tho, no state is copied in the creation, all methods are stateless.

Then i can add the wrapper in the nms class like the bukkit entity and use that.

[JustDoom]

Was there anything else that needed to be added or is it just waiting for a review?