fix: fix CI

[antoniolocascio]

What ❔

Pin zerocopy version to avoid compilation issue

Why ❔

Is this a breaking change?

• Yes
• No

Checklist

• PR title corresponds to the body of PR (we generate changelog entries from PRs).
• Tests for the changes have been added / updated.
• Documentation comments have been added / updated.
• Code has been formatted.

[AntonD3]

To do so, it add the Cargo.lock

But do we really need Cargo.lock for it? Isn't pinning certain version enough?

[antoniolocascio]

@AntonD3 it is, it just wasn't working bc I added the pin to workspace deps without any crate actually using it. I had to add it as an explicit dep to basic_system for it to work. We can remove the Cargo.lock now, but should we?

[AntonD3]

We can remove the Cargo.lock now, but should we?

I would remove the lock for workspace, AFAIK, it's a good practice for library crates/crates used by others, because Cargo.lock is ignored for crate when you are importing it. So, you know, it's better to always build it without Cargo.lock(locally/in CI) to be sure that it will be compiled successfully when imported as a dependency

[antoniolocascio]

@AntonD3 good point, removed the top-level Cargo.lock