update dependency requirements

We should use caret for dependencies so that crates that are below
1.0 releases only automatically fetch path releases during the build.

Similarly, crates that are >= 1.0 release, update to new patch & minor
versions.

Signed-off-by: Andreea Florescu <[email protected]>

Author: andreeaflorescu

crates/virtio-queue-ser/Cargo.toml

@@ -10,9 +10,9 @@ license = "Apache-2.0 OR BSD-3-Clause"
 edition = "2018"
 
 [dependencies]
-serde = { version = ">=1.0.27", features = ["derive"] }
-versionize = ">=0.1.6"
-versionize_derive = ">=0.1.3"
+serde = { version = "1.0.27", features = ["derive"] }
+versionize = "0.1.6"
+versionize_derive = "0.1.3"
 # The `path` part gets stripped when publishing the crate.
-virtio-queue = { path = "../../crates/virtio-queue", version = ">=0.4.0" }
-vm-memory = ">=0.8.0"
+virtio-queue = { path = "../../crates/virtio-queue", version = "0.5.0" }
+vm-memory = "0.8.0"