VMware: fail module when unable to find the user specified folder

[thefaftek]

SUMMARY

Updating this to provide logs if a null/non-existent folder is presented. Currently the error message you receive is "msg": "Failed to move VM with exception 'NoneType' object has no attribute 'MoveInto'". This does not describe the issue occurring.

This purely looks at the folder variable after it reaches out to VMWare, and if the value is null exists instead of attempting a move using a null folder.

ISSUE TYPE

• Bugfix Pull Request

COMPONENT NAME

vmware_guest_move

ADDITIONAL INFORMATION

1. Attempt to move a VM using the below playbook, with an invalid folder path
2. Review output.

Playbook:
- hosts: localhost
  gather_facts: false
  connection: local
  vars:

  tasks:
  - vmware_guest_move:
      datacenter: "{{datacenter}}"
      username: "{{ vcenter_username }}"
      password: "{{ vcenter_password }}"
      hostname: "{{vcenter_hostname}}"
      validate_certs: no
      name: "{{inventory_hostname}}"
      dest_folder: "{{dest_folder}}"

BEFORE: 
VM move fails, error "msg": "Failed to move VM with exception 'NoneType' object has no attribute 'MoveInto'"

Afterwards the VM move succeeds with standard success message.

[ansibot]

cc @Akasurde @Tomorrow9 @ckotte @dav1x @imjoseangel @lparkes @warthog9
click here for bot help

[ansibot]

@thefaftek, just so you are aware we have a dedicated Working Group for vmware.
You can find other people interested in this in #ansible-vmware on Freenode IRC
For more information about communities, meetings and agendas see https://github.com/ansible/community

click here for bot help

[Akasurde]

@thefaftek Thanks for the contribution.