Fix problem with certificates in presence of ALIEN_PROC_ID
In GRID environments a problem was found using CCDB and libjalienO2 when ALIEN_PROC_ID was set.
Apparently the issue is that multiple calls to libjalienO2 lead to a certificate filename collision since ALIEN_PROC_ID is no longer sufficient to distinguish instances.
This commit unifies the code for create "safe und unique" tmp filenames: a) no custom treatment for ALIEN_PROC_ID b) create safe filenames based on pid + random session id + instance counter