For #25587 - Spaces in Windows PC & Python paths are now supported.

Spaces are now supported in paths for Pipeline Configurations on Windows when using the latest version of the tank.bat file.  Additionally, Python can now be installed into a path with spaces in (e.g. C:\Program Files) if needed.
Actually that is being overkill and just a sign of my laziness! However, In my opinion, what could perhaps be useful is 

```
rem -- now get path to python interpreter by reading config file
rem -- (the usebackq tokens syntax is used to handle spaces in the path correctly)
for /f "usebackq tokens=*" %%G in ("%INTERPRETER_CONFIG_FILE%") do (SET PYTHON_INTERPRETER=%%G)
```

is that any better? More useful?