refactor: use cwltool loader for standardized cwl doc handling

[amaltaro]

Fixes #108

With this pull request, we adopt the cwltool loader functionality to normalize and handle CWL documents, instead of manually juggling with fields and different data types.

Tested with pixi run dirac-cwl-run test/workflows/crypto/description.cwl --print-workflow, where exactly the same workflow visualization is retained.
Also added some unit tests that can be triggered with pixi run pytest test/test_job_executor.py

[aldbr]

Thanks for your contribution!
I just have some minor comments 🙂

[aldbr]

Just wondering if getattr is not misleading in this context, as I think the cwl instance you get will always have cwlVersion, doc, inputs, .... To double check, but I think they just exist with default value like None or [] if nothing is provided.

This would likely work:

Suggested change

	cwl_version = getattr(cwl, "cwlVersion", "Unknown")
	cwl_version = cwl.cwlVersion # default value is likely 1.2, to double check
	cwl_version = cwl.cwlVersion or "Unknown" # if there is no default value

[amaltaro]

Thank you for the review, @aldbr .
Yes, directly accessing the object attributes should work as well. However, the getattr adds some protection in case the attribute changes for any reason (bug, non-backward compatible changes, etc).

What is the preferred behavior for this module:
a) have a clear exception being raised in case one of the expected attributes is not to be found?
b) or to gracefully deal with this with getattr and default values?

Given that this is already in a try/except block, I think option a) (which is your suggestion) is better. But better to get a confirmation please.

[ryuwd]

We discussed and we think the first option is the way to go

[aldbr]

I guess this comment is not true anymore?

Suggested change

# Show final outputs (handle both dict and list formats)

[amaltaro]

@ryuwd @aldbr I applied the changes requested during review.

However, one of the CI tests fails with an error unrelated to this PR:
https://github.com/DIRACGrid/dirac-cwl/actions/runs/30002435046/job/89190520820?pr=130

It looks like another PR that has recently been merged is not failing these unit tests (commit message length). Please let me know how to proceed here and/or how to retrigger CI tests.