Destructor name again : compilation issue with gcc...

There appears to be a pb in 9df8c9da.

For a template class, A::B::C<T1,T2>
the destructor name was C<T1,T2>
leading to code like
A::B::C<T1,T2>::~C<T1,T2>()

which does not compile on gcc (4.6, 4.7), also it seems to be correct code ...
clang and intel C++ compile it, but not gcc.

I changed the name to generate the code :

A::B::C<T1,T2>::~C()

which compiles on gcc, clang, intel

by further cutting the <...> in the destructor name.

reduce code overhead for tuple constants by using PyTuple_Pack() instead of step-by-step tuple construction code

fix early module registering by using FQMN instead of plain module name, added test for init-time reloading of modules in packages

--HG--
extra : transplant_source : Y%1C%3A%07%2C%60%B0%F0.%EA%B1%23%3F%0E%20%89%13%C5%C24

--HG--
extra : transplant_source : %F9%FF%8Ai%99OV%BFd%F7%147%19pm%5D%DF%98%D4%FC

in Py3.3, use new PyImport_ImportModuleLevelObject() C-API function instead of equivalent Python call to __import__()