MidnightNameplates 0.9.5 - Phase 9.5 Rule Priority & Conflict Resolver

NEW CONFLICT RESOLUTION
- Deterministic rule ordering.
- Priority order:
  CRITICAL > HIGH > NORMAL > LOW
- Tie-break modes:
  SPECIFICITY (more conditions wins)
  ORDER (earlier rule wins)
- Optional field merging:
  different matching rules can own different presentation fields.

NPC FIELD OWNERSHIP
- scale
- alpha
- health color
- frame color
- name color
- marker
- aura visibility
- cast visibility
- execute warning
- emphasize / de-emphasize

SPELL FIELD OWNERSHIP
- cast color
- cast border color
- emphasize
- glow
- pulse
- scale
- flash near end
- sound flag/name
- text warning

BEHAVIOR
- Higher-priority rules own a field before lower-priority rules.
- If priorities tie and tie-break=SPECIFICITY, the rule with more active conditions wins.
- Final fallback is stable rule order.
- If field merging is disabled, one overall winning rule controls the full presentation.

CONFIG
/mnp -> Rules -> Conflict Resolution
- Enable conflict resolver
- Prefer higher priority
- Allow field merging
- Tie-break mode

TEST
1. Two NPC rules for same NPC with LOW and CRITICAL priority.
2. Verify CRITICAL wins overlapping fields.
3. Give LOW a field CRITICAL does not set; with field merging ON it should still apply.
4. Disable field merging; only overall winner should apply.
5. Same-priority rules with different condition specificity.
6. Repeat with spell rules.
7. Existing single-rule behavior remains unchanged.
8. No Lua/taint/secret-value errors.
