use virtio-queue from crates.io to prevent dupes in Cargo.lock

[aghecenco]

Summary of the PR

Use the published virtio-queue to prevent unwanted duplicates in Cargo.lock when consuming both am unpublished device and a released virtio-queue.

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.

[epilys]

@aghecenco looking at the CI failures, and it seems virtio-queue contains unpublished changes (we bump the version when we make a new release). So unfortunately this might not be possible as long as the crates are developed in the same repository.

Can you give more info re: Cargo.lock and duplicates? perhaps there's another solution to your problem.