Fix action_hook for vagrant 2.2.14

[aki2o]

This fix is for #8
This trouble looks to be caused by changing timing to call vagrant action hooks after vagrant 2.2.14
I tried to fix config for action_hook with the following way.

• Avoid append hook
• Select a hooked action which looks good timing in builtin actions for before after hook
• Reverse after hook definition order because after hook looks to be called order by desc

And, the following some misc fixes be included

• Call RemoveConfig with keeping in step with other actions
• Fix console output
• Quit RemoveConfig on suspend and halt because I feel we still need ssh config on their timings

This fix works in my environment but I'm hesitating by the following reasons.

• Probably this fix works only for virtualbox
  • I selected a hooked action with refering https://github.com/hashicorp/vagrant/blob/v2.2.14/plugins/providers/virtualbox/action.rb
  • But, I noticed uncalled actions exists in https://github.com/hashicorp/vagrant/blob/v2.2.14/plugins/providers/docker/action.rb
• Probably my choice hooked actions are private api
• I feel this trouble is vagrant bug
  • I can't find document about hook for developer other than https://www.vagrantup.com/docs/plugins/action-hooks
  • And, it describes called after the machine has entered the up state. So, I feel append hook is OK
  • But, I can't find the change log or commit of vagrant which causes this trouble.

[dasginganinja]

This applies after #8 ? I just merged that in.