feature(CI): Test de CI 1.0.0b0

chore(debugging): Ajout de journalisation d'erreur et d'un example de…

… stack docker-compose.

Removed validation pattern for postgresql identifiers in json-schema …

…resources.

PostgreSQL identifiers syntax is very dependant on locale and server settings.

Remove time intersection from pairing process (#10)

## Changelog   
### [Changed]
* `pair_from_sources`: the pairing function now matches declarations to
detections only according to spatial intersection. The date comparison
actually contradicted the goal to describe soil occupation at the time
of the detection.
* `pair_from_sources`: database objects marked for deletion are now
logged alongside their deletion reason.
* `pair_from_sources`: some pairing statistics other than deletions are
now logged as debug entries

### [Fixed]
* `pyproject.toml`: changed ruff configuration keys to follow a
deprecation warning
* `delete_data`: If the input id list is empty, instead of sending an
invalid SQL request, deletion functions now exit before attempting
anything

Objects deletion tool and various fixes (#9)

## Changelog
### [Added]
* `delete_data` executable : cascade delete objets from any table,
following lists of identifiers.
* SQL structures initialisation scripts:
* one file dedicated to `declaration` raw data import (target for
`import_declaration`)
* one file for the main structures used by the pairing tool
(`pair_from_sources`)
* not tested : `delete_data` may probably work only on the main
structures (because of the cascade deletion)

### [Changed]
* functions from `delete_data` module are used by `pair_from_sources`.
* `declaration` input data specifications changes were implemented in
`import_declarations`
* `import_declaration` is more permissive and imports any delcaration
dossier from source. Use of two different tables, schema or database
(your choice) is recommended to distinguish between the following:
* raw imported `declaration` data: simple SQL extraction of the remote
source data
* filtered partial `declaration` data: used for pairing and further
visualisation.

### [Fixed]
* `detection` objects' geometries construction method created invalid
multipolygons. (contained polygons shared edges) Now the construction
process ensures the geometry's validity.
* Miscommunications on `detection` input data specs caused SQL insertion
errors. The table definition has been modified to ensure a unique
integer identifier.

Fixed invalid geometry composition in import_declarations. (#8)

## Changelog
### [Added]
* Table definitions SQL file for reference.

### [Fixed]
* `import_declarations` imports a declaration geometry as a
GeometryCollection instead of an invalid MultiPolygon

bumpversion configuration correction

Fix: made database entities identifiers validation schema much more p…

…ermissive, to match both SQL and postgresql specifications.

GitHub workflow permission change to make publication work. Try numbe…

…r 2.

GitHub workflow permission change to make publication work.