Allow NVDA build system to still function if NvDA repository is moved or copied to another location (#12184)
* venvUtils\ensureAndActivate.bat: rather than calling the standard activate.bat from the generated .venv, set the necessary environment variables manually, and make VIRTUAL_ENV be relative to this script, rather than a hard-coded path.
This allows the NVDA repository to be moved or copied somewhere else on the same system and the environment used without having to be recreated.
* Don't call the deactivate script from venvCmd.bat. We no longer call activate.bat so deactivate.bat may do the wrong thing. But more importantly, we already call endlocal which dumps all changes to the environment anyway, thus it is not needed.
* Add extra comments to venvCmd.bat explaining setlocal / endlocal.
* ensureAndActivate.bat: add more clearer comments, mentioning .venv's standard activate.bat.