Fix build on Windows with recent Python versions

[Yaribz]

• support new Python library name format on Windows during auto-detection (libpython.a --> python.lib)
• fix error "fileparse(): need a valid pathname at Makefile.PL line 174." introduced by commit bedc5820 when Python libraries are not found automatically (this error prevented accessing the interactive mode to try to workaround the problem manually !)
• avoid selecting the limited Python API library (ABI) by default on Windows (fix missing symbols error)
• naive workaround for weird race condition on some Windows versions happening between "rmtree" and "mkdir" calls in 00init test (when re-running the tests)
• skip test 35dictunicodememleak on Windows as the "rss" field is not provided by the Proc::ProcessTable module on Windows (on Windows, test should be rewritten using Win32::API module and calling getProcessMemoryInfo from psapi.dll instead)

[Yaribz]

I close this 2 years old pull request as it seems there is no interest in it, I will just continue using my own fork on Windows.

[niner]

Oh, sorry, I just forgot about it. I probably didn't have time to review it immediately and then the email was no longer unread and it became one of the 20K old mails in my inbox. Obviously my work management sucks...

[Yaribz]

Thanks but actually most of the changes included in this PR can no longer be applied like this, due to the revamps that occurred in the makefile one year after. I would revert this merge because it goes against the new logic of detecting the python version first to build a fixed library name instead of scanning the dir... (see the $version variable which is built but never used in the special_get_libpath function after this merge...).