Added a way for CL to prevent/modify damage from OnCharacterDamaged

[ninj1337]

Creating this as an example of one way for the Custom Logic OnCharacterDamaged callback to prevent damage (for the character owner only).

Instead of only calling OnCharacterDamaged from NotifyDamagedRPC, we now only call it there for clients who are not the owner. For the character owner, OnCharacterDamaged is instead called before damage is even applied. This enables these callbacks to use the new Character.CustomDamageReceivedEnabled and Character.CustomDamageReceived fields (which mirror the Character.CustomDamageEnabled and Character.CustomDamage fields) to modify received damage before it is actually applied. If the damage is modified to 0, the hit is fully cancelled; character health is not modified and other clients are not even notified of the hit.

The ability to modify or cancel damage from the receiving end (rather than only from the attacking end) allows CL to modify damage using data that the attacker does not own (and therefore does not have realtime access to), such as whether or not the attacked player is invincible. Combined with Character.CustomDamage, it allows data owned by both clients to participate in damage calculations.

[ninj1337]

Didn't think too hard about these names, there is probably something clearer to call them

[ninj1337]

This may be controversial, since GetDamagedRPC did not previously return early if damage == 0, however, I think modifying damage to 0 from CL should have consistent results whether or not the damage was from GetHitRPC or GetDamagedRPC.

[ninj1337]

PLEASE NOTE: I removed the early return here where CustomLogicManager.Evaluator == null.

This means that the Game Feed section below will still run in that case. I assume that was an oversight since I can't see why the Game Feed shouldn't still be updated, but I just wanted to point out the potential change in behavior which is unrelated to the main changes.