Use sudo --non-interactive in at_exit to not hang

I noticed that ruby-bench hangs after a long enough benchmarking
session. Turns out it was sudo trying to ask for with `quiet: true`.
Since it may hang trying to ask for input during exit, let's use
`--non-interactive` to opportunistically re-enable turbo boost.

Author: XrXr

lib/cpu_config.rb

@@ -67,7 +67,7 @@ class IntelCPUConfig < CPUConfig
   def disable_turbo_boost
     # sudo requires the flag '-S' in order to take input from stdin
     BenchmarkRunner.check_call("sudo -S sh -c 'echo #{TURBO_DISABLED_VALUE} > #{NO_TURBO_PATH}'")
-    at_exit { BenchmarkRunner.check_call("sudo -S sh -c 'echo 0 > #{NO_TURBO_PATH}'", quiet: true) }
+    at_exit { BenchmarkRunner.check_call("sudo --non-interactive sh -c 'echo 0 > #{NO_TURBO_PATH}'", quiet: true) }
   end
 
   def maximize_frequency
@@ -114,7 +114,7 @@ class AMDCPUConfig < CPUConfig
   def disable_turbo_boost
     # sudo requires the flag '-S' in order to take input from stdin
     BenchmarkRunner.check_call("sudo -S sh -c 'echo #{TURBO_DISABLED_VALUE} > #{BOOST_PATH}'")
-    at_exit { BenchmarkRunner.check_call("sudo -S sh -c 'echo #{TURBO_ENABLED_VALUE} > #{BOOST_PATH}'", quiet: true) }
+    at_exit { BenchmarkRunner.check_call("sudo --non-interactive sh -c 'echo #{TURBO_ENABLED_VALUE} > #{BOOST_PATH}'", quiet: true) }
   end
 
   def maximize_frequency