(hashicorp#9775) Move triggers object init in machine

Prior to this commit, the hyper-v provider called an action on a machine
that hadn't fully finished initializing. This commit fixes that by
moving up the initialization of the triggers object next to the rest of
the instance variables of the machine object.

lib/vagrant/machine.rb

@@ -110,6 +110,7 @@ def initialize(name, provider_name, provider_cls, provider_config, provider_opti
       @ui              = Vagrant::UI::Prefixed.new(@env.ui, @name)
       @ui_mutex        = Mutex.new
       @state_mutex     = Mutex.new
+      @triggers        = Vagrant::Plugin::V2::Trigger.new(@env, @config.trigger, self)
 
       # Read the ID, which is usually in local storage
       @id = nil
@@ -149,8 +150,6 @@ def initialize(name, provider_name, provider_cls, provider_config, provider_opti
       # Output a bunch of information about this machine in
       # machine-readable format in case someone is listening.
       @ui.machine("metadata", "provider", provider_name)
-
-      @triggers = Vagrant::Plugin::V2::Trigger.new(@env, @config.trigger, self)
     end
 
     # This calls an action on the provider. The provider may or may not

test/unit/vagrant/machine_test.rb

@@ -76,6 +76,11 @@ def new_instance
       expect(subject.id).to be_nil
     end
 
+    it "should initialize the trigger object" do
+      subject = new_instance
+      expect(subject.instance_variable_get(:@triggers)).not_to be_nil
+    end
+
     describe "as a base" do
       let(:base) { true}