tests: add rust-vmm-ci-tests.json pipeline

[stefano-garzarella]

Summary of the PR

This is based on rust-vmm-ci/.buildkite/test_description.json. We can't run rust-vmm-ci tests because they enable all the features with --all-features and our crates have features that may not be compatible with others (e.g. xen). Waiting to solve this problem in rust-vmm-ci (see https://github.com/rust-vmm/rust-vmm-ci/issues/152), we use a custom pipeline based on that but that does not use --all-features.

Requirements

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

• [x] All commits in this PR are signed (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.

[stefano-garzarella]

v2:

• Shortened the test names because they are needed in DOCKER_PLUGIN_CONFIG for some configurations

[stefano-garzarella]

For now I have left the rust-vmm-ci pipeline active, but as soon as we merge this one I will deactivate it.

[stefano-garzarella]

Should we run clippy and cargo test also with default features? Or cargo build is enough? (for now I just tried to replicate rust-vmm-ci, so maybe we can think about that later)

[Ablu]

Should we run clippy and cargo test also with default features? Or cargo build is enough? (for now I just tried to replicate rust-vmm-ci, so maybe we can think about that later)

I do not mind. So let's keep it simple? Probably time is better spent on trying to solve https://github.com/rust-vmm/rust-vmm-ci/issues/152 :).