Fix staging and resume for typed record inputs with nested Path fields

[stekaz]

Typed process inputs using record types with nested Path fields are (currently) not always handled like normal file inputs.

For example, given an input such as:

input:
sample: SampleRecord

where SampleRecord.path is a Path, the compiler should implicitly stage sample.path into the task work directory and rewrite references such as:

${resource.path}

to the process working directory, for example:

input.txt

But in some cases this does not happen. The compiler can miss the implicit file stager for nested Path fields. When that happens, task scripts either render the original source path instead of the staged task-local path, or the expected file could be missing from the working directory. And -resume could behave incorrectly.

[netlify]

✅ Deploy Preview for nextflow-docs-staging canceled.

Name	Link
🔨 Latest commit	b90b274
🔍 Latest deploy log	https://app.netlify.com/projects/nextflow-docs-staging/deploys/69f2044b29d5560009fa1cb3

[bentsherman]

Is this related to #7032 ?

[stekaz]

Yes - I think they're both in the same problem area, but the failure modes are different. This PR fixes the input-side staging/localization (and resume) for typed records with nested Path fields. The other issue occurs when a record input is reused in an output record causing the downstream process to receive paths that are only valid in the upstream context.