[BUG]: Union enable_tagging=1 writes union_history.dat to run directory instead of output directory

[NoeB]

Describe the bug
A clear and concise description of what the bug is.

When Tagging is enabled for a Union Component:

COMPONENT master = Union_master(enable_tagging=1)
It writes the output file: union_history.dat to the current directory instead of the output files directory.

In my opinion it should also be written to the output files directory so that all run related output files are stored in the same directory. But maybe there is also a reason to have in the run folder.

Document steps to reproduce the bug
Steps to reproduce the behavior:
Enable Tagging:
COMPONENT master = Union_master(enable_tagging=1)
and run a simulation with Union_components the union_history.dat file will appear in the run directory
Expected behavior
A clear and concise description of what you expected to happen.
I would expect it to be stored in the output directory along with the other Detector/Simulation output files
Screenshots
If applicable, add screenshots to help explain your problem.

OS and McStas/McXtrace version (please complete the following information):
Every version

Add your code / dataset
If applicable:

• Please provide a zip-archive of instrument plus any local components, datafiles, …
• Please provide all settings used (e.g. input parameters, mpi parallelisation level, …)
• Please provide a zip-archive of your dataset

Additional context
Add any other context about the problem here.

[willend]

@NoeB thanks for the issue and related PR. I will chat with @mads-bertelsen about it but I am inclined to take it more or less 'as is'.

[mads-bertelsen-agentic]

It's certainly neater to have it in the output directory, thanks! I have received very few questions about this feature, what is your use-case for it? Glad to hear its getting some use!

[NoeB]

@mads-bertelsen-agentic I am working on modelling different Pressure Cells at PSI with McStas and McStasScript and started having a look at the more advanced options provided by the union components. So for me It was useful to compare changes done on the instrument and seeing the results in my plots but also in this trace history if it translates into the changes I would expect.