bug 1579902: mozrunner: supply mozprofile version dependency; r=webdriver-reviewers,jgraham

Depending on mozprofile by relative path makes it hard to publish
mozrunner to crates.io because cargo is unable to work out the
version range the crate needs.

By specifying both a path and a semver range we ensure mozrunner
uses the in-tree version of mozprofile when building locally,
and the upstream crates.io version when published and used elsewhere.

This means this version number must be bumped every time a new
(backwards incompatible) mozversion is released.

It is debatable whether the version range should be exact, i.e. "0.6.0",
but I opted to go with "0.6" which is how I would normally define
a crate dependency.  As long as mozprofile continues to follow the
principles of semantic versioning this should be fine.

Differential Revision: https://phabricator.services.mozilla.com/D45511

--HG--
extra : moz-landing-system : lando

testing/mozbase/rust/mozrunner/Cargo.toml

@@ -8,7 +8,7 @@ license = "MPL-2.0"
 
 [dependencies]
 log = "0.4"
-mozprofile = { path = "../mozprofile" }
+mozprofile = { path = "../mozprofile", version = "0.6" }
 plist = "0.5"
 
 [target.'cfg(target_os = "windows")'.dependencies]