serialize as str when field is UUID type

[juggler31]

Il y avait des warnings lors de la sérialization d'un objet UUID.

[coveralls]

coverage: 77.583% (-0.06%) from 77.647%
when pulling c21c3fa on serialize_uuid
into 6395159 on master.

[Copilot]

Pull request overview

This PR addresses UUID serialization warnings by serializing uuid.UUID values as strings, and updates CI to adjust the Python/Django test matrix and GitHub Actions versions.

Changes:

• Serialize uuid.UUID fields as str in _serialize_field to avoid JSON serialization warnings.
• Remove Python 3.7 from the GitHub Actions matrix and update Actions used in the workflow.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
tracking_fields/tracking.py	Adds explicit UUID handling in field serialization.
.github/workflows/python-app.yml	Updates Python version matrix and bumps GitHub Actions versions.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The matrix exclude list was previously excluding Python 3.7 for Django 4.x (unsupported). Now that 3.7 is removed from the matrix, these entries were changed to exclude Python 3.8 instead, which is a supported combination for Django 4.0/4.1/4.2 and is also covered in tox. This unintentionally drops CI coverage for Python 3.8 on Django 4.x; remove these exclude items (or adjust them to only exclude truly unsupported pairs, e.g. Django 4.0 with Python 3.11).

[Copilot]

This adds special-casing for uuid.UUID serialization, but there is no test asserting the resulting stored values (and that the warning log path is no longer used). Please add/extend a test that tracks a UUIDField (or tracks the UUID primary key) and asserts the persisted TrackedFieldModification JSON contains the plain UUID string rather than a UUID('...') repr, and ideally that no serialization warning is emitted.