Update Vhost-device-can dependency on socketcan and move it in the main workspace

[TimosAmpel]

Summary of the PR

This PR updates the socketcan-rs dependency of vhost-device-can device and moves it on the main workspace.

Specifically by updating the socketcan-rs dependency to "v3.3.1" this PR solve the following issues noted in the Cargo.toml of the vhost-device-can:

• socketcan-rs "v3.3.0" includes the following issue related to CANFD messages reception:
  • https://github.com/socketcan-rs/socketcan-rs/pull/61.
• If rust version "1.80" is used, the compiler might complain about "std::mem::size_of":
  • https://github.com/socketcan-rs/socketcan-rs/pull/72

Requirements

Before submitting your PR, please make sure you addressed the following requirements:

• [x] All commits in this PR have Signed-Off-By trailers (with git commit -s), and the commit message has max 60 characters for the summary and max 75 characters for each description line.
• [x] All added/changed functionality has a corresponding unit/integration test.
• [x] All added/changed public-facing functionality has entries in the "Upcoming Release" section of CHANGELOG.md (if no such section exists, please create one).
• [x] Any newly added unsafe code is properly documented.

[TimosAmpel]

I think the two commits can be squashed, there's no reason to update Cargo.lock separately is there?

Generally LGTM!

Thanks for your review @epilys. Yes indeed I agree, I just merged everything in one commit. SInce the last push I have also modified the coverage value under staging so the CI succeeds after moving vhost-device-can, let me know if that's ok.

[epilys]

@TimosAmpel looks good. you can drop the Update licenses' symlinks for vhost-device-console commit since it's part of https://github.com/rust-vmm/vhost-device/pull/758

[epilys]

@TimosAmpel fyi you can (and probably should since this is your device) leave reviews in https://github.com/rust-vmm/vhost-device/pull/758 and other PRs in general even if you're not a maintainer. They just don't count towards the "two approving reviews required" limit.

[TimosAmpel]

@TimosAmpel fyi you can (and probably should since this is your device) leave reviews in #758 and other PRs in general even if you're not a maintainer. They just don't count towards the "two approving reviews required" limit.

@epilys Thanks for pointing that out. Yes, I will review the changes done the next days