Fixed curio related logspam

[Saereth]

#2085 and #2040
Added null-safety checks:

1. Check if curioInv.isEmpty() before calling .get()
2. Check if livingArmourSockets == null before using it

[wrincewind]

I've had a look and am unable to replicate this issue in live - i'm not seeing logspam on death, or when wearing living armour, or when playing in a small pack wth Corail Tombstone. Were you able to replicate this issue before deploying your fix, and if so, how?

As far as i know this was fixed by #2045, for reference.

[Saereth]

The Problem is the original code - assumes everything exists
ICurioStacksHandler livingArmourSockets = CuriosApi.getCuriosInventory(player).resolve().get().getCurios().get("living_armour_socket");

This chain fails if:

• resolve() returns an empty Optional -> .get() throws NoSuchElementException
• The "living_armour_socket" slot doesn't exist -> returns null, then next operation NPEs
  Optional<ICuriosItemHandler> curioInv = CuriosApi.getCuriosInventory(player).resolve();

if (curioInv.isEmpty()) { return 0; } // Guard #1
ICurioStacksHandler livingArmourSockets = curioInv.get().getCurios().get("living_armour_socket");`

if (livingArmourSockets == null) { return 0; } // Guard #2

Why it helps:

• Returns early with 0 instead of crashing/spamming logs
• Handles edge cases like Curios not being fully initialized, or the slot type not being registered yet, or having been removed.

Hope that clears it up, happy to elaborate more if needed