feat: Add extensions available in DoorType

[GoldenPig1205]

Description

Describe the changes
Added extensions available in DoorType and modified some of the behavior of functions that existed in the existing DoorType.

What is the current behavior? (You can also link to an open issue here)
There were 3 extension functions (IsGate(), IsCheckpoint(), IsElevator()) and they were working fine.

What is the new behavior? (if this is a feature change)
Added 8 extension functions (IsHID(), IsScp(), IsEscape(), IsLcz(), IsHcz(), IsEz(), IsSurface(), IsUnknown()).
All extension functions belonging to DoorType now derive bool values ​​from String values.

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

Other information:
This PR does not change the way existing features work. It also does not change the result.
Even if the DoorType enum is added, you don't need to manually update the extension functions of DoorType.

This PR is possible because DoorType names follow a set of rules.

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

[VALERA771]

I don't think that this is neccecary. Yes, our code looks cleanier but optimisation is not very good. It's faster to compare 2 integers rather that enumerate with Contains. Also list takes memory and comparing not