[8.0] fix: do not reset files for not yet submitted jobs

[atsareg]

The removed operation was reseting files to Unused for tasks that were created but job not yet submitted. As a result new jobs were created for the same files multiple files.

A fix was needed in the pre-commit configuration for the flynt part as by default it uses python3.14 version not compatible with 3.11. I think this should be harmless

BEGINRELEASENOTES

*Transformation
FIX: WorkflowTasks - do not reset files for not yet submitted jobs

ENDRELEASENOTES

[fstagni]

Looking at this PR, I realize that there is the "same" function in https://github.com/DIRACGrid/DIRAC/blob/rel-v8r0/src/DIRAC/TransformationSystem/Client/RequestTasks.py#L366

which is certainly working fine (in the context of replication transformations, but still...). Can you compare the 2 and check their differences?

[atsareg]

Yes, this is a good confirmation of this PR. In the replication transformations the files are ONLY checked for tasks that were created and got the ExternalID:

DIRAC/src/DIRAC/TransformationSystem/Client/RequestTasks.py

Line 389 in d20f5d9

# Only consider tasks that are submitted, ExternalID is a string

.

Here, there should be the same logic: files are reserved while the jobs are not yet submitted, those should not be reset to UNUSED because it is just a slow job submission in an overloaded system.

[fstagni]

@arrabito and @zhangxiaomei can you evaluate this one? Is it by chance something that you hotfixed?