feat(license): wrap GET /license/export-csv endpoint

[Valyrian-Code]

Refs #52.

Adds LicenseEndpoint.export_licenses_csv() for GET /license/export-csv — the export counterpart to the merged import_licenses_csv() (#185). Returns the exported licenses as CSV text and accepts an optional license id (0 = all).

API details

Verified against Fossology 4.4.0 (API 1.6.1) running in a container.

Tests

• export → import round-trip — passes live. Idempotent, and robust because the export output is exactly what import_licenses_csv() expects.
• Mocked 403 error path.

ruff and mypy pass; the export tests pass against a live fossology 4.4.0 container.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[deveaud-m]

@Valyrian-Code thanks again for the PR.

Could you also add a test to verify that single license can also be exported using the "id" parameter?

And verify that the exported csv the expected number of licenses contains?

[Valyrian-Code]

Thanks @deveaud-m! Added in a213d69:

• test_export_single_license_by_id — exports a single license via the id parameter and asserts the CSV contains exactly that one license (header row + one data row).
• test_export_all_licenses_returns_more_than_one — asserts the full export (no id) returns more than a single license.

Both verified live against a Fossology 4.4.0 container.

One note on "expected number": I did not assert the full-export row count against list_licenses(), because export-csv returns a broader set than the paginated license list (871 rows vs 779 from list_licenses(all_pages=True) on 4.4.0), so an exact-equality check would be misleading. The single-license export is asserted exactly (1 row).

[Valyrian-Code]

Hi @deveaud-m, thanks again for the reviews on these.

Most of what I've sent has been merged now: the report endpoints (#178, #184), the license CSV import (#185), and the upload analysis + agents endpoints (#197, #198). I'd like to get more involved in fossology-python beyond sending the occasional PR.

Happy to help with:

• larger features or refactors
• issue triage
• reviewing other contributors' PRs

Is there a good way to get more regularly involved?