test: Rely on release process for version sync

When we switch to `cargo-release`, it will validate that the auto-update
was performed.  No reason to have an extra dependency during
development.

Cargo.toml

@@ -119,7 +119,6 @@ backtrace = { version = "0.3", optional = true }
 [dev-dependencies]
 regex = "1.0"
 lazy_static = "1"
-version-sync = "0.9"
 criterion = "0.3.2"
 # Cutting out `filesystem` feature
 trycmd = { version = "0.8.0", default-features = false, features = ["color-auto", "diff", "examples"] }

clap_generate/Cargo.toml

@@ -35,7 +35,6 @@ clap = { path = "../", version = "=3.0.0-beta.5", default-features = false, feat
 
 [dev-dependencies]
 pretty_assertions = "1.0"
-version-sync = "0.9"
 clap = { path = "../", version = "=3.0.0-beta.5", default-features = false, features = ["std", "derive"] }
 
 [features]

clap_generate/tests/version-numbers.rs

@@ -1,6 +0,0 @@
-use version_sync::assert_html_root_url_updated;
-
-#[test]
-fn test_html_root_url() {
-    assert_html_root_url_updated!("src/lib.rs");
-}

tests/version-numbers.rs

@@ -1,11 +0,0 @@
-use version_sync::{assert_html_root_url_updated, assert_markdown_deps_updated};
-
-#[test]
-fn test_readme_deps() {
-    assert_markdown_deps_updated!("README.md");
-}
-
-#[test]
-fn test_html_root_url() {
-    assert_html_root_url_updated!("src/lib.rs");
-}