Review handling of logs for operational executions

As discussed offline with @nperez and @ptrascas, I am opening this to keep track of a potential issue related to operationals. When there are multiple executions under the same output directory, the log files get rewritten each time:

[vagudets@bsceshub03 logs]$ ls
atomic_recipe_sys-NCEP-CFSv2_ref-ERA5_var-prlr_reg-EU_sdate-20250911.log
atomic_recipe_sys-NCEP-CFSv2_ref-ERA5_var-prlr_reg-Iberia_sdate-20250911.log
atomic_recipe_sys-NCEP-CFSv2_ref-ERA5_var-rsds_reg-EU_sdate-20250911.log
atomic_recipe_sys-NCEP-CFSv2_ref-ERA5_var-rsds_reg-Iberia_sdate-20250911.log
atomic_recipe_sys-NCEP-CFSv2_ref-ERA5_var-sfcWind_reg-EU_sdate-20250911.log
atomic_recipe_sys-NCEP-CFSv2_ref-ERA5_var-sfcWind_reg-Iberia_sdate-20250911.log
atomic_recipe_sys-NCEP-CFSv2_ref-ERA5_var-tasmax_reg-EU_sdate-20250911.log
atomic_recipe_sys-NCEP-CFSv2_ref-ERA5_var-tasmax_reg-Iberia_sdate-20250911.log
atomic_recipe_sys-NCEP-CFSv2_ref-ERA5_var-tasmin_reg-EU_sdate-20250911.log
atomic_recipe_sys-NCEP-CFSv2_ref-ERA5_var-tasmin_reg-Iberia_sdate-20250911.log
atomic_recipe_sys-NCEP-CFSv2_ref-ERA5_var-tas_reg-EU_sdate-20250911.log
atomic_recipe_sys-NCEP-CFSv2_ref-ERA5_var-tas_reg-Iberia_sdate-20250911.log
main.log
recipes

If we want to keep the logs of all executions, they should be given a unique ID that is separate from the ID associated with the output directory.

Victòria