Add c++ name mangling to avoid keyword collision

[cmalinmayor]

https://github.com/live-image-tracking-tools/geff/actions/runs/26179372787/job/77017880290

28 compilation failures in our GEFF windows tests, where apparently we call an attribute uint16 and windows c++ breaks on keyword collision - Claude suggested adding this attribute name mangling to the c++ side only, avoiding keyword collision without affecting the public Python API

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.11%. Comparing base (bd4c275) to head (968f976).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #50      +/-   ##
==========================================
+ Coverage   95.03%   95.11%   +0.07%     
==========================================
  Files          12       12              
  Lines         383      389       +6     
==========================================
+ Hits          364      370       +6     
  Misses         19       19              

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[tlambert03]

thanks @cmalinmayor! I'll have a look at this today (if the test failures are unrelated, let me just touch up the repo again)

[cmalinmayor]

Claude says witty needs typing_extensions in it's dependencies, hence the failures that are on main. Seems like the fix doesn't actually work on the Windows CI though (I couldnt' test locally), so I'll need to iterate

[tlambert03]

ok, I'll do the updates in parallel

[cmalinmayor]

Alright the fix seems to work now, and the general approach of mangling c++ keywords that are passed from user-specified attributes into the c++ template seems like a good idea to avoid other unforeseen issues

[codspeed-hq]

Merging this PR will not alter performance

✅ 6 untouched benchmarks

---

_{Comparing windows-name-collision-fix (968f976) with main (bd4c275)}

[tlambert03]

thanks @cmalinmayor, good fix 👍

[tlambert03]

just pushed tag v0.0.6 ... so this should be released shortly