attempt to autocorrect port mapping if it occurs on up
- defaults to true in servers.yaml
- doesn't appear to be too reliable, currently fails for me and throws the following warning before attempting to install, rather than fail silently with the locally bound port overriding the forwarded brooklyn port:
```
==> brooklyn: Clearing any previously set forwarded ports...
Vagrant cannot forward the specified ports on this VM, since they
would collide with some other application that is already listening
on these ports. The forwarded port to 8081 is already in use
on the host machine.
To fix this, modify your current project's Vagrantfile to use another
port. Example, where '1234' would be replaced by a unique host port:
config.vm.network :forwarded_port, guest: 80, host: 1234
Sometimes, Vagrant will attempt to auto-correct this for you. In this
case, Vagrant was unable to. This is usually because the guest machine
is in a state which doesn't allow modifying port forwarding.
```
- Updated the Vagrantfile to point the user at `servers.yaml` when they search for the suggested line in the warning above.
2 files changed
