fix: Escaping Exiled and LabAPI bug different way

[MS-crew]

Description

Describe the changes
Exiled Broken Labapi event fix different way

What is the current behavior? (You can also link to an open issue here)

What is the new behavior? (if this is a feature change)
Because the previous fix broke the custom item escape handler or other conditions that check isallowed. Instead, I brought isallowed to normally return false and not break labapi. Now it comes after exiled labapi, and if isallowed is not true, it can return without breaking labapi.

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No

Other information:

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