Upgrade to clarity 5.0.1 (re-land #95 with the entity filter fix)

[spheenik]

This re-applies #95, which was reverted in #96, and moves from clarity 5.0.0 to 5.0.1. 5.0.1 fixes the bug behind the no field for class ... at ... failures reported in #95.

Cause

The bug was in clarity's new entity filter, which #95 turns on. Sometimes a replay creates an entity of a class the filter skips at an index that still holds an entity the filter keeps (for example CDOTA_Item_Rune). Clarity skipped the new entity but didn't remove the old one. The next update at that index was then decoded with the old entity's class, and the parse failed. Which class appears in the error depends on which entity was left over, which is why the reported class names varied. Only some replays reuse an index this way, which is why only a share of parses failed.

Fix

Clarity 5.0.1 now deletes the old entity in that case. The fix is skadistats/clarity@bcb08e5. This PR adds nothing beyond #95 except the version bump.

Verification

• Replay 9028583612, the one from the report on Upgrade to clarity 5.0.0: ~2× faster parsing, ~2/3 less allocation #95, fails with 5.0.0 and parses with this branch, with the entity filter on.
• At the clarity level, I compared the full entity state with the filter on and off, tick by tick, on 45 Dota 2 replays with two different filters, one of them this parser's. The kept entities matched on every tick.
• I did not repeat Upgrade to clarity 5.0.0: ~2× faster parsing, ~2/3 less allocation #95's byte-identical output comparison against master for this branch. The parser code is identical to Upgrade to clarity 5.0.0: ~2× faster parsing, ~2/3 less allocation #95.

If anything still goes wrong, -Dopendota.entityFilter=false turns the filter off without a redeploy of new code.

🤖 Generated with Claude Code