[FEATURE] Add support to `Cargo/Crates` - Rust

[guibranco]

Description

We need to create a Rust package (crate) for this repository and publish it to Crates.io, Rust’s official package registry. Publishing the repository as a Rust package will streamline distribution and versioning, allowing developers to easily integrate it into their projects via Cargo.

Why We Need This

1. Easy Installation: Making the project available as a crate allows developers to add it as a dependency in their Cargo.toml, simplifying the installation process.
2. Version Control: Publishing the crate to Crates.io supports versioning, enabling developers to depend on specific versions of the package.
3. Distribution: Crates.io is the central repository for Rust libraries, making it easier for other developers to discover and use the package.

Steps to Proceed

Here’s a step-by-step guide on how to package and publish the repository as a Rust crate:

1. Prepare the Cargo.toml File:

   • Ensure the Cargo.toml file contains the necessary package metadata such as the name, version, description, authors, and license.
   • Add dependencies and other configurations if needed.
   • Refer to the official Cargo documentation for more details on configuring the Cargo.toml file: Creating a Cargo Package.

2. Check Code for #![no_main] or #[lib] (If Required):

   • Ensure the project is set up as a library crate if it’s not a binary crate. A library crate allows other projects to use it as a dependency.

3. Run cargo package to Verify the Crate:

   • Run cargo package to verify that the package can be successfully built. This command will simulate packaging the project and ensure all files are in place.

4. Publish to Crates.io:

   • Before publishing, ensure you have a Crates.io account.
   • Use cargo login to authenticate with your API token.
   • Once you’re logged in, run the following command to publish the crate to Crates.io:

     cargo publish

     Detailed instructions on publishing to Crates.io are available here: Publishing on Crates.io.

5. Update Documentation:

   • Once published, ensure the README file includes instructions on how to add the crate to other projects.
   • Add a badge to the README that links to the Crates.io page for easy access to the package.

Additional Notes

• Consider adding unit tests or examples to the crate to help developers quickly understand how to use it.
• Ensure the project follows Rust’s best practices for crate publishing.

Tech notes

• https://doc.rust-lang.org/cargo/guide/creating-a-new-project.html
• https://web.mit.edu/rust-lang_v1.25/arch/amd64_ubuntu1404/share/doc/rust/html/cargo/guide/creating-a-new-project.html
• https://rust-cli.github.io/book/tutorial/packaging.html

Additional information

No response