feat(rln): publish rln crate

[s1fr0]

Given the current maturity of the rln module and the different applications relying on it, we want to publish new releases as crates to, e.g. crates.io.

This will allow to push further rln functionalities, while allowing projects relying on it to easily integrate/point to a specific rln release.

To ensure stability in terms of functionalities of the published crate during time, we need to ensure that all dependencies (and dependencies of dependencies) have fixed revision.

This issue is blocked by #97, since a license is required when publishing crates.

It makes sense to publish the rlncrate once zerokit release v0.2 is ready, i.e. #100 is complete.

Acceptance criteria

• Addressing Check and add licenses #97;
• Ensure all dependencies (and dependencies of dependencies) have fixed revision; chore(rln): ensure all dependencies have fixed revision #126
• Publish the rln crate to e.g. crates.io.