Add ability target type data

[hassayag]

Abilities have target data relating to how it is cast and which types of units it can be casted on. These include the following properties from an ability in raw data - m_eAbilityTargetingLocation, m_eAbilityTargetingShape, m_eAbilityActivation, m_nAbilityTargetTypes. These should then be stored in the output ability data using appropriate naming

[LVL1024]

@hassayag Was thinking of working on this and was looking through the abilities and noticed there's a bit more than the ones you listed. Was wondering if you think there's a use for grabbing these as well, or just get the 4 you listed?

• m_AbilityBehaviorsBits: It answers questions like: Is it a projectile? Can it be channeled? Does it require a target?
• m_eAbilityType: The primary category of the ability (e.g., EAbilityType_Ultimate, EAbilityType_Signature). The parsers already filters for this but it might be useful to store in the output.
• m_nAbilityTargetFlags: Provides exceptions to targeting rules, like whether an ability can target invulnerable/invisible enemies.
• m_bitsInterruptingStates: Defines which character states (like Stunned or Silenced) interrupt an ability.
• m_nBehaviors: A projectile-specific bitmask that defines the physics of a projectile (e.g., if it bounces off walls). This would only be parsed if the ability has the PROJECTILE behavior flag.
• m_eDebuffType: Classifies the type of debuff an ability applies, which could be useful for understanding dispel interactions.
• m_nAbilityPointsCost & m_nAbillityUnlocksCost: Defines the cost to learn or upgrade the ability.