Fix can_i_damageable creation

[mtwango]

• check, whether CCItemDamageable has been placed in the world before calling tick (Custom Item with can=can_i_damageable error #1422)

[cbnolok]

What about adding an ASSERT(pItem != nullptr)? It shouldn't happen but if it does it's a null pointer dereference and it will cause the server to crash, so i'd be extra sure (i know it wasn't there even before, this would be a good moment to fix that as well).
Reading the other CComponentsProps, actually it would be a wise idea to add an ASSERT directly in each one's GetLink() method, provided we aren't using it in places where we expect a possibly null pointer, which i don't think we are doing

[mtwango]

I've seen GetLink() methods on Champion, Spawn and ItemDamageable. Do you mean to assert pItem existence in each of them?

[cbnolok]

It might be worth adding that assert inside GetLink, yes, what do you think about it?

[mtwango]

Yeah, good idea, especially at spawns. Added and tested on local save, no errors.