Fix hash when CmdEvalParam as output

[jorgee]

close #5470

Adds the CmdEvalParams in the task outputs as a key to compute the hash

[netlify]

✅ Deploy Preview for nextflow-docs-staging canceled.

Name	Link
🔨 Latest commit	3ec20f0
🔍 Latest deploy log	https://app.netlify.com/projects/nextflow-docs-staging/deploys/68879e7b3b38c100083980bd

[pditommaso]

This alter the assumption the task is idempotent. The task hash should only rely on the inputs not on the outputs

[pditommaso]

I see the point it could be considered as part of the execution script, but still in principle it should not be needed to re-run the task

[bentsherman]

Considering that eval is a shorthand for export an output env var in the script, it is essentially part of the script and therefore part of the task identity.

I think it is possible to evaluate the task outputs without "resolving" or "collecting" them, before computing the task hash. Then you can see if any output evals were declared and include them as if they were part of the script

[pditommaso]

This needs to be marked as a cache breaking change in the changelog

[pditommaso]

also I really not sure about this, because break the contract that task ID depends only on inputs + script

[bentsherman]

The eval commands are part of the script