Fix Friendly Fire rules

[x3rt]

Description

Describe the changes
Fixes CheckFriendlyFirePlayerRules to account for when Friendly Fire is enabled

What is the current behavior? (You can also link to an open issue here)
https://discord.com/channels/656673194693885975/1269192577475674213

What is the new behavior? (if this is a feature change)
Friendly Fire rules are respected.

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No. Only thing that will change is that Friendly Fire servers will be able to flash their teammates as they are supposed to be able to in base-game. (Just like grenades)

Other information:
I could possibly just return true instead of HitboxIdentity.IsDamageable as it would immediately return true anyways when FriendlyFire is enabled.
Could also replace calls to Server.FriendlyFire || CheckFriendlyFirePlayerRules with just CheckFriendlyFirePlayerRules, but that is up to you.

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

[Misaka-ZeroTwo]

@louis1706 @Jesus-QC we should just return true directly?

awaiting opinions

[Misaka-ZeroTwo]

dup with #33

[x3rt]

dup with #33

Hmm I didn't see this PR.
Unsure why they are returning false though as NW logic is HitboxIdentity.IsDamagable (which would immediately return true when FriendlyFire is enabled)

[iamalexrouse]

If a PR with these changes already exists, this PR can possibly be closed, otherwise, Is this going to be updated?