Fix regressions in the fusion provider introduced by veewee#596.

I stumbled across two problems with the recent change to the ip address detection for vmware fusion in 2e4a50f611cac93d16079c24ad8fd63fd967ee36:

1. `vmrun` was called without the full path which doesn't work without modifying the PATH variable
2. As briefly mentioned in the pull request the change broke the `fusion build` command because the new method doesn't work at that stage.

As also already suggested in the pull request by @jedi4ever I tried to fix 2. by chaining the different methods of ip adress detection.