Make dynflow an explicit dependency

Loading the smart_proxy_dynflow (or any Smart Proxy plugin really) in
load_classes does not work due to the way plugin initialization happens.
For this plugin to work, dynflow must be running. This uses requires to
validate that dynflow is actually correctly enabled and running. This
also means that if dynflow was loaded but ended up in a failed state
that REX SSH also ends up in a failed state.

Author: ekohl

lib/smart_proxy_remote_execution_ssh/plugin.rb

@@ -60,6 +60,8 @@ class Plugin < Proxy::Plugin
 
     plugin :ssh, Proxy::RemoteExecution::Ssh::VERSION
 
+    requires :dynflow, '~> 0.5'
+
     load_classes do
       require 'smart_proxy_dynflow'
       require 'smart_proxy_dynflow/task_launcher'

test/integration_test.rb

@@ -27,7 +27,9 @@ def test_features_for_default_mode_without_dynflow
 
     mod = response['ssh']
     refute_nil(mod)
-    assert_equal('running', mod['state'], Proxy::LogBuffer::Buffer.instance.info[:failed_modules][:ssh])
+    assert_equal('failed', mod['state'], Proxy::LogBuffer::Buffer.instance.info[:failed_modules][:ssh])
+    assert_equal("Disabling all modules in the group ['ssh'] due to a failure in one of them: 'dynflow' required by 'ssh' could not be found.",
+                 Proxy::LogBuffer::Buffer.instance.info[:failed_modules][:ssh])
   end
 
   def test_features_for_default_mode_with_dynflow