Add python3.13-dev to Dockerfile for ARM64 wheel builds

[Naragod]

Proposed Changes

The markus_exam_matcher==0.4.0 depends on zxing-cpp==2.3.0 (a C++ extension). zxing-cpp==2.3.0 exclusively publishes wheels for x86_64 and i686 Linux. aarch64 wheels are missing.

Here is what is happening:

• Python packages with C/C++ code (like zxing-cpp) ship precompiled wheels for common platforms to reduce user effort.
• zxing-cpp==2.3.0 publishes wheels for many linux_x86_64 (Intel Linux) and few linux_aarch64 (ARM Linux).
• On an Intel Mac, Docker runs x86_64 Linux containers. pip finds a matching wheel and installs it directly. Zero compilation required.
• On Apple Silicon, Docker runs aarch64 Linux containers. pip fails to find a matching wheel, and downloads the source tarball to try and compile the C++ extension locally.

Solution:

• Building a C/C++ Python extension from source requires the Python C API headers (Python.h, pyconfig.h, etc.) and the shared library to link against.
• The python3.13 package exclusively includes the interpreter runtime, enough to run Python.
• python3.13-dev provides those headers and libraries. Without it, the C++ compiler is unable to find Python.h and the build fails.
• With it installed, cmake/gcc can compile zxing-cpp from source successfully inside the container.

Type of Change

(Write an X or a brief description next to the type or types that best describe your changes.)

Type	Applies?
🚨 Breaking change (fix or feature that would cause existing functionality to change)
✨ New feature (non-breaking change that adds functionality)
🐛 Bug fix (non-breaking change that fixes an issue)
🎨 User interface change (change to user interface; provide screenshots)
♻️ Refactoring (internal change to codebase, without changing functionality)
🚦 Test update (change that only adds or modifies tests)
📦 Dependency update (change that updates a dependency)
🔧 Internal (change that only affects developers or continuous integration)

Checklist

(Complete each of the following items for your pull request. Indicate that you have completed an item by changing the [ ] into a [x] in the raw text, or by clicking on the checkbox in the rendered description on GitHub.)

Before opening your pull request:

• I have performed a self-review of my changes.
  • Check that all changed files included in this pull request are intentional changes.
  • Check that all changes are relevant to the purpose of this pull request, as described above.
• I have added tests for my changes, if applicable.
  • This is required for all bug fixes and new features.
• I have updated the project documentation, if applicable.
  • This is required for new features.
• If this is my first contribution, I have added myself to the list of contributors.

After opening your pull request:

• I have updated the project Changelog (this is required for all changes).
• I have verified that the pre-commit.ci checks have passed.
• I have verified that the CI tests have passed.
• I have reviewed the test coverage changes reported by Coveralls.
• I have requested a review from a project maintainer.

Questions and Comments

(Include any questions or comments you have regarding your changes.)

[david-yz-liu]

@Naragod this change is good and thanks for the detailed info. Please update the changelog as well

[Naragod]

@Naragod this change is good and thanks for the detailed info. Please update the changelog as well

Done.

[coveralls]

Coverage Report for CI Build 24697496610

Coverage remained the same at 91.713%

Details

• Coverage remained the same as the base build.
• Patch coverage: No coverable lines changed in this PR.
• No coverage regressions found.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

No coverage regressions found.

---

Coverage Stats

Relevant Lines:	48561
Covered Lines:	45278
Line Coverage:	93.24%
Relevant Branches:	1854
Covered Branches:	959
Branch Coverage:	51.73%
Branches in Coverage %:	Yes
Coverage Strength:	130.75 hits per line

---

💛 - Coveralls