bug: license metadata mismatch — Python binding declares LGPL-2.0 but library is GPL-3.0

[grzanka]

Part of #108 (health-review epic).

Problem

python/pyproject.toml declares:

license = {text = "LGPL-2.0-or-later"}

But the C library is GPL-3.0-or-later everywhere else:

• COPYING is GPLv3,
• the README license badge says GPLv3,
• CMakeLists.txt CPACK RPM metadata sets CPACK_RPM_PACKAGE_LICENSE "GPL-3.0-or-later".

Since the Python package links the GPLv3 native library at runtime, declaring it LGPL-2.0 is inconsistent and potentially incorrect from a licensing standpoint. This needs a deliberate decision, not a silent default.

Proposed change

Decide the intended license for the Python binding (most likely GPL-3.0-or-later to match the linked library) and make it consistent across python/pyproject.toml, any python/README.md license note, and the wheel metadata. If a different license is genuinely intended, document the rationale.

Acceptance criteria

• License declared in python/pyproject.toml matches the project's actual/intended license and is consistent with COPYING, README, and packaging metadata.
• The decision/rationale is recorded (commit message or a short note in python/README.md).