[#102] Cargo deny workflow

[robertmercea]

cargo-deny workflow

Integrated cargo-deny in the build-and-test GitHub Action

Description

• Added cargo-deny workflow to build_and_tests_reusable.yaml
• Added deny.toml config file with accepted licenses for the project
• Updated crossbeam-channel and tokio packages as they had issues detected by cargo-deny

Fixes #102

---

Type of change

New feature (non-breaking change which adds functionality)

---

Checklist:

• I have performed a self-review of my code
• I have tested my code on different platforms (if applicable)
• I have commented my code, particularly in hard-to-understand areas
• I have added necessary documentation (if appropriate)
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

Additional context

There are many duplicate packages in the project, detected by cargo-deny. I did not do anything about them, however, as that could cause everything to break.
I have also noticed that there are two unmaintained packages in the project (derivative and instant), but they are dependencies of other packages used by rencfs.

[radumarias]

allow only these:

    "MIT",
    "Apache-2.0",
    "BSD-3-Clause"

[radumarias]

#308 (comment)

based on detail ok the above link, it makes sense. our repo states only the first 3, maybe we should check the other licenses requirements if we need to explicitly mention them in our license info to, can you please do that?
we could mark the conversation as resolved after that

[robertmercea]

CC0 1.0 does not need to be mentioned whatsoever according to this EU site
Zlib states that mentioning the license is "appreciated, but is not required" according to opensource.org and their website
ISC, however, requires that we mention it according to their website and opensource.org. This license is almost identical to the MIT license.