Potentially dangerous (on clusters) temp-file naming policy in Writer.predict_Fstat()

In debugging some confusing behavior/problems of pyFstat on a cluster, I noticed that the method predict_fstat() of the class Writer, in make_sfts.py:257 uses the 'label' argument to construct the filename for the temporary internal file ('temporyFile') in the user's home-dir they launched the jobs from. This is potentially confusing/dangerous, as it's not documented (I believe) and as there's also the argument 'outdir', which is more obvious to be required to be unique on cluster runs. What can happen here is that someone uses the same label for all jobs of a cluster run, gives every job a unique 'outdir', and still jobs will fall over themselves when all trying to read-read-delete the same temporary file in predict_fstat().

As as fix I would simply suggest to place that temporary file inside the 'outdir' as well, then there should be no problems.