feat(import): add smart parsing for Nimble Nexus action descriptions

[trevlar]

Summary

• Adds intelligent parsing of monster action descriptions from Nimble Nexus API to build proper effect trees
• Replaces hardcoded 'bludgeoning' damage type with smart extraction from multiple text patterns
• Creates SavingThrowNode and ConditionNode effects based on action description content
• Extracts range/reach/cone/line/burst information from descriptions

Changes

New Files:

• descriptionParser.ts - Parsing utilities for damage types, saving throws, conditions, and range/reach
• descriptionParser.test.ts - Comprehensive test suite with 132 tests using real Nimble Nexus API data

Modified Files:

• constants.ts - Added DAMAGE_TYPE_MAP, SAVE_TYPE_ABBREVIATION_MAP, and CONDITION_MAP
• types.ts - Added ParsedSavingThrow, ParsedCondition, ParsedDamage, and ParsedRangeReach interfaces
• NimbleNexusParser.ts - Integrated buildEffectTree() into createActionItem()

Supported Patterns

Pattern	Example	Result
Damage type in formula	"5d8+13 Radiant"	damageType: radiant
Damage type in description	"fire damage"	damageType: fire
Save with damage	"DC 15 DEX save or 4d6 fire"	SavingThrowNode + DamageNode
Save for half	"DC 21 DEX save for half"	halfOnSave: true
Condition on hit	"On hit: [[Slowed]]"	ConditionNode in on.hit
Condition on crit	"On crit: Poisoned"	ConditionNode in on.criticalHit
Range in description	"(Range: 8)"	targets.distance: 8
Cone/Line/Burst	"Cone 6", "Line 10x2"	template shape

Test plan

• All 132 description parser tests pass
• All 407 tests across the full codebase pass
• Import various monsters from Nimble Nexus in FoundryVTT and verify effect trees
• Test damage rolls show correct damage types
• Test saving throw buttons appear for save-based actions
• Test conditions apply on appropriate triggers (hit, crit, failed save)

[Fronix]

@trevlar

• Import various monsters from Nimble Nexus in FoundryVTT and verify effect trees
  • Works for the most part, we are in the hands of people not writing novels in the damage sections so there are still some that fail. We could probably work a bit with nimble.nexus and ask for a foundry-mode that puts stricter rules on the creation of the monster, then we could promote those in the importer to be more "safe to work as intended".
    Another way would be if nimble nexus used foundry-type patterns.
• Test damage rolls show correct damage types
  • The ones that are imported as actions work, even more advanced ones. Though, many get created as simple actions but it will probably be hard to catch all here, not a deal breaker for merge.
  • Tutor, Teaching Golem
  • Caerys, the Hollow Star
  • Thor, God of Thunder
• Test saving throw buttons appear for save-based actions
  • Tested with Thor, God of Thunder's Call Lightning
• Test conditions apply on appropriate triggers (hit, crit, failed save)
  • Crits works fine
  • On hit works fine
  • Not sure about the save part, I tested Tutor, Teaching Golem's

  Fiiiire Ball! (1/use).
  5d6.
  Aoe, Range 8, 5x5. DEX Save DC 11. On Failure: Full damage and target gains Smoldering. On Success: Half Damage.

They get imported as shared rolls instead of on fail/pass save