Add GitHub Actions CI pipeline with upstream libinjection integration

[Copilot]

No CI existed to validate the Python bindings against upstream libinjection changes, making regressions invisible until manually caught.

Changes

• .github/workflows/ci.yml — new pipeline with:
  • Triggers: push/PR to main/master + weekly schedule (Monday UTC) to surface upstream breakage automatically
  • Matrix: Python 3.8–3.12, fail-fast: false
  • Full build chain per run: clone upstream (--depth=1), copy C sources, generate words.py via json2python.py, run SWIG, build extension in-place, run pytest test_driver.py -v
  • Symlink ../tests → upstream/tests to satisfy test_driver.py's hardcoded relative path resolution
  • permissions: contents: read for least-privilege GITHUB_TOKEN

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Add pipeline tests</issue_title>
<issue_description>Create a new pipeline to test that the module works with upstream changes. It should use github actions for python and get the files from upstream.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Add pipeline tests #8

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.