Create acl-anthology release v0.5.4

[mbollmann]

The sole purpose of this release is to provide one crucial bit of functionality needed for transitioning to the new author system: reading & writing ORCIDs recorded in the XML.

Longer explanation:

• The transition script (for moving to the new author system) must be run with a version of the library that still uses name_variants.yaml, since this gives us the name resolution logic under the old system.
• v0.5.3 of the library doesn’t yet support reading or writing ORCIDs recorded in the XML, but we have now already started adding them. This means they can’t be accessed and would in fact be erased if we used that version for the transition.
• python-dev already contains all the updates for the new author system, so we cannot use that branch for the transition either.

Making a new release backporting only the ORCID serialization seemed like the cleanest solution to me.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.76%. Comparing base (b6c257a) to head (111694c).
⚠️ Report is 198 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #6653      +/-   ##
==========================================
+ Coverage   92.03%   93.76%   +1.72%     
==========================================
  Files          35       35              
  Lines        2850     2853       +3     
==========================================
+ Hits         2623     2675      +52     
+ Misses        227      178      -49     

Files with missing lines	Coverage Δ
python/acl_anthology/people/name.py	97.85% <100.00%> (+0.04%)	⬆️

... and 5 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[mbollmann]

Ugh, the MacOS build error was painful to debug. Turns out that the Poetry action uses the system Python rather than the version specified in the runner, so it was trying to install Scipy via Python 3.14 even though we currently only test with 3.10–3.13. I followed the solution in abatilo/actions-poetry#72 and squashed my 7 commits that were trying to get this to work...

(I should put "Python 3.14 support" on my list of TODOs for the next release.)