#26741: [desktop] Update the project python bootstrap to reset PATH

Make sure applications are launched with the proper DllDirectory set.
Is that common? I did find some stuff: 
http://stackoverflow.com/questions/7238403/import-win32api-error-in-python-2-6
https://code.google.com/p/winpython/issues/detail?id=78

If we are anticipating that our clients will hit win32api import error this for some reason, then I think the outer exception trap is cool - however, if we are doing it just to be cautious, I don't think this is the right approach; That means that something else will/may go wrong (in this case, the desktop engine not correctly unloading its DLLs), potentially leading to other issues down the line. Now as you start troubleshooting those issues, it won't be obvious what the actual problem is, because it is hidden. Instead, if we didn't have the outer exception trap, the user would get an error : could not import win32 module - still an error - but this time we know what is wrong straight away. The user can troubleshoot more easily and/or if the contact our support and give us the error message, we know what is going on right away. Does that make sense? 

I guess what I am saying is that my opinion here is that unless we have strong reasons (which in that case should probably be mentioned as comments in the code), we shouldn't utilize this kind of catch-em-all approach to error checking - it often leads to scenarios which can be tricky to troubleshoot and debug!

Hope it makes sense! :)