Port unique updater scripts from PoB2

[EtherealCarnivore]

Summary

Ports the unique item updater scripts from PathOfBuilding-PoE2 (PRs #54, #65, #175), building on the work started in #8700 by @Wires77. Extends coverage to all 20 PoE1 item types and fixes multiple bugs found during testing.

New scripts

• uTextToMods.lua -- converts unique item text to mod IDs (run when adding new uniques)
• uModsToText.lua -- converts mod IDs back to text from GGPK data (run when game data updates)

Changes to existing files

• mods.lua -- adds ModItemExclusive.lua and ModTextMap.lua generation
• statdesc.lua -- handles ! negation limits and ranges starting/ending at 0

Bug fixes over original PoE2 scripts

• uModsToText.lua: last item in each file wasn't getting mods flushed (no separator at EOF)
• uModsToText.lua: mod ID regex misidentified base type names containing hyphens (e.g. "Two-Point Arrow Quiver") as legacy mod ranges
• uModsToText.lua: unresolved text lines lost their position among stat-ordered mods
• uModsToText.lua: nil access on statOrder when processing legacy-only mods
• uTextToMods.lua: greedy {.+} tag stripping consumed multiple tags; fixed to lazy {.-}
• uTextToMods.lua: mod selection logic could skip better matches; separated into two-pass approach
• uTextToMods.lua: usedMods was global; modTextMap reloaded inside loop unnecessarily
• Enabled all 20 PoE1 item types (original only had axe enabled with PoE2 types commented out)

Bug fixes in Item.lua (pre-existing)

• excluded/exclude variable name mismatch creating an accidental global (lines 103-143)
• Wrong Lua pattern ^%[a ]+ corrected to ^[%a ]+ for jewel radius parsing
• Space indentation converted to tabs in jewel radius block

Data update

• All unique item text files re-exported with current GGPK data
• Adds stat ordering, updated mod wording, and catalyst tags for amulets/rings

Addresses review feedback from @Nightblade on #8700. Supersedes #8700.

Test plan

• Full test suite: 195/195 passing, 0 failures
• No "unrecognised item" warnings during load
• PoB loads and runs without errors
• Spot-check unique items in PoB UI for correct mod display
• Verify catalyst tags on amulets/rings are accurate

[Wires77]

I'm going to push some changes to this branch to start fixing a lot of these uniques:

• Reverted the changes to the unique text files themselves, as they were missing tags and other things. Going through each item type one-by-one is a lot more maintainable and until then we don't want to lose the original text.
• Updated the scripts to remove several PoE2-exclusive concepts/tags
• Overhauled the TextToMods script to be more robust and accurate

Even with these changes, I'm just going to go through each item type one at a time so they can be inspected thoroughly without one-shotting the whole thing. There are a lot of manual fixes that are needed, which is why the uTextToMods script was left out of the PoE2 one. At the end I'll probably disable it again once we have the mod files in a good state.

I'm even considering commenting out the statOrder sorting to make diffs more readable until we know the text and parsing itself is in a good state. Would've been nice, but it's too much code to bother with. The ordering might actually help find the correct mods too.

Known issues:

• Mods don't get converted to generic parsing unless it's a variant. So far this has been most visible on old prophecy uniques, because their base unique got a variant, but obviously we didn't add one for the upgraded version
• permyriad type stats are a bit flaky and I probably missed some
• Mods with multiple lines of stats are not handled at all. Usually this results in the first line being properly converted to a mod, leaving the others. Then when it's converted back into unique text, you have duplicate lines
• Added flat lightning mods aren't getting legacy values applied. Probably fixable, but so far I've been fixing manually
• "Reduced" and "Less" legacy mods aren't getting their negative signs in the values

[Wires77]

One thing that is near-impossible to automate is when GGG did the base item implicit upgrade. The mods are full of implicits like this:

Implicits: 2
{variant:1}ElementalDamagePercentImplicitSceptreNew16[10,10]
{variant:2,3}ElementalDamagePercentImplicitSceptreNew16

When you search on the trade site and sort by the implicit, you'll see that the 10% implicits are really 20%, and are likely ElementalDamagePercentImplicitSceptre1 for a mod. You still have to put the legacy brackets in for that, which is why it likely won't matter for our use case unless they go back and update those old implicit values.

[PJacek]

I did some work here: https://github.com/PJacek/PathOfBuilding/tree/port-unique-updater
The updated script reads how many implicits there are in the input file and outputs the number of implicit lines actually written.

[EtherealCarnivore]

Added jewels on top of body armour, boots, and gloves. Rest of the item types (helmets, shields, quivers, belts, rings, amulets) still to go - skipping flasks and tinctures since someone else is on those.

[EtherealCarnivore]

Re-exported body, boots, gloves, and jewel through the full pipeline on Windows:

1. Ran uTextToMods.lua (Data -> Export) to convert remaining raw text lines to mod IDs
2. Ran uModsToText.lua (Export -> Data) to regenerate Data files with proper stat ordering and legacy mod resolution

Had to use Windows for this since uModsToText.lua needs dat() from the GGPK to resolve legacy mods with [min,max] ranges - those can't be stubbed out on macOS.

Test suite: 194/195 passing (1 pre-existing TradeQueryCurrency failure, unrelated).

[Wires77]

There are a bunch of duplicated lines in these latest commits, due to the multiline bullet in my other comment. The output should look nearly identical to the existing item unless there are some mod changes we didn't catch in earlier leagues.

We'll also want to commit the Export/Uniques file for future automation

[Wires77]

Check your output for duplicated lines. These already exist above, because the one mod is three lines in one.

[Wires77]

One last thing I've noticed on a handful of mods is that GGG has set their value to 0, like this section for Lightpoacher explains on the wiki. This affects us by making the mod not appear at all in ModItemExclusive, so we can't describe it. Could look into making them appear there, but otherwise I've just left the raw text in Export/Uniques

[EtherealCarnivore]

Fix multi-line mod handling in export round-trip
Rewrote io.linesBackward to read the whole file into memory instead
of the old chunk-based approach - the 4KB-chunk reader broke on
Windows because text-mode \r\n conversion threw off the seek math,
producing garbled lines at chunk boundaries.