Removed lib/inspec/utils/latest_version.rb and associated code.

There is no reason why our tests should be failing because we deploy a
new version. That test shouldn't even be hitting the network for real.

Besides, the functionality has no place in our codebase. It's
functionality provided via `gem outdated` so why did we re-implement
it? And we expect most people to be running via omnibus, so they're
pinned to a specific version in the first place. Even if they updated,
they still couldn't run it and that would be more confusing.

Signed-off-by: Ryan Davis <zenspider@chef.io>

lib/inspec/cli.rb

@@ -385,14 +385,7 @@ def version
       v = { version: Inspec::VERSION }
       puts v.to_json
     else
-      require "inspec/utils/latest_version"
       puts Inspec::VERSION
-      # display outdated version
-      # TODO: remove this. Don't notify of update to a gem when they install omnibus
-      latest = LatestInSpecVersion.new.latest || Inspec::VERSION
-      if Gem::Version.new(Inspec::VERSION) < Gem::Version.new(latest)
-        puts "\nYour version of #{Inspec::Dist::PRODUCT_NAME} is out of date! The latest version is #{latest}."
-      end
     end
   end
   map %w{-v --version} => :version

test/functional/inspec_test.rb

@@ -7,10 +7,7 @@
     it "provides the version number on stdout" do
       out = inspec("version")
 
-      # Tolerate working on an out of date branch
-      output = out.stdout.split("\n").reject { |l| l.start_with?("Your version of InSpec is out of date!") }.join("\n") + "\n"
-      output.must_equal Inspec::VERSION + "\n"
-
+      out.stdout.must_equal Inspec::VERSION + "\n"
       out.stderr.must_equal ""
 
       assert_exit_code 0, out