feat: support CURIES in config

[cmdoret]

due to the lack of inference, tripsu configs can be very redundant.
To reduce this redundancy, we could support compact uris using something like this in the config file:

prefixes:
  "schema": "<https://schema.org/>"
  "ex": "<http://example.org/>"

nodes:
  of_type:
    - "schema:Person"
    - "schema:Organization"

objects:
  on_type_predicate:
    "schema:Person":
        - "schema:birthPlace"
  on_predicate:
     - "ex:password"
     - "ex:email"
     - "ex:userName"

[supermaxiste]

When looking for crates to carry out the task, I first checked sophia and the only thing I found was about IRIs: https://docs.rs/sophia_iri/0.9.0/sophia_iri/index.html
Otherwise there seems to be a (relatively new) crate dedicated to cURIs: https://lib.rs/crates/curies

Unless there's a strong opinion, I'd go for the second option since it seems to be fitting the cause (even though very very new).

[supermaxiste]

Expand ont eh Rules struct with an optional prefixes field.
Have impl on Rules struct to:

• Expand cURIes when prefixes are there (+test)
• Throw an error when cURIes are there but no prefixes are provided (+test)

Important: be consistent in the formatting of the URI, CURIES crate doesn't use <>, https://biopragmatics.github.io/curies.rs/getting-started/#loading-prefix-maps

[supermaxiste]

Switch from curies to https://github.com/endoli/curie.rs/tree/main

[supermaxiste]

I made some pretty decent progress on this feature and I have to admit that it looks easier in theory than in practice.

This is the high-level flow of the PR so far:

flowchart TD    
    return(Return expanded cURIs)
    flow(Normal tripsu flow)
    rules.yaml --> has_valid_curies_and_uris
    has_valid_curies_and_uris --> |no| Error
    has_valid_curies_and_uris --> |yes| return
    return --> flow

Loading

The code for has_valid_curies_and_uris is in place with a bunch of functions to:

1. Make sure full URIs are compliant with sophia_iri:IRI
2. Make sure cURIes are "expandable" based on the prefixes provided

The missing pieces and to dos are the following:

• A .filter function for Rules to select cURIes or URIs depending on the downstream code
• Tests for:
  1. No prefixes provided, cURIes in the config --> FAIL
  2. Prefixes provided, cURIes using an undefined prefix --> FAIL
  3. Prefixes provided, no cURIes in the config --> PASS
  4. Prefixes provided, cURIes using them --> PASS
  5. Valid URIs in the config --> PASS
  6. Invalid URIs in the config --> FAIL