Localize environment changes in vagrant.bat with SETLOCAL

I use vagrant regularly in Windows.  In the past I've encountered some issues cause by environment variables not being properly reset in vagrant.bat.  These have since been fixed. 

Using SETLOCAL should prevent these problems in the future as it keeps all environment changes local to the batch file run.  When the batch file exists, the environment goes back to what it was before.