CWL guidance improvements + Multipart Deploy/Replace

[fmigneault]

Summary

This PR improves CWL guidance in the DRU extension by fixing incorrect conformance references and adding practical multipart request examples. I also fixed a few formatting items encountered along the way in DRU.

Changes

• Fixed invalid CWL references (mixup of rc_ogcapppkg to rc_cwl) in CWL deploy/replace requirement bodies.
• Added multipart CWL recommendations for deploy and replace.
  • Rather than leaving it up to interpretation and having people implementing it in various ways, provide an explicit example and recommendations.
• Added a multipart deployment example with various relevant combinations/considerations.
  • Included start root-part selection and Content-ID / cid: host+UUID reference patterns.
  • Included Content-Disposition filename-based part mapping examples.
  • Included Content-Location remote-reference variant in multipart example.
• Clarified CWL execution unit handling/media-type interpretation
  (e.g.: dealing with encoding vs registered application/cwl, application/cwl+json, application/cwl+yaml media-types and their implications in by-ref vs by-value submission)
• Updated DRU references to HTTPS (align with Changes to address issues raised during the JAN-2026 OAProc Code Sprint #547).

Future Considerations

• Using the proposed multipart/related, it might be possible to better improve the unification between Part 1, Part 2 DRU, and Part 3 Ad-hoc workflows using CWL. More specifically, the same multipart/related for the "Deploy" parts might be supplemented by another "Execute" application/json part. A single workflow execution request could then dynamically run the provided workflow and inputs/outputs requirements.

  The updates provided in this PR would define the "main chuck" of the workflow "Deploy" similarly across Part 2 and Part 3. Therefore, Part 3 would just need to merge Part 2 "Multipart CWL Deploy" with "Core Execute" to define the ad-hoc CWL in a very concrete fashion.

  • Relates to Ad-hoc CWL workflows not applicable #500

  • Follow-up PR to be done if ⬆️ sounds good for all.

@pvretano @gfenoy @jerstlouis FYI