improvements for Colletion Output responses, nested processes workflows and dataClasses/profiles

[fmigneault]

Changes

• Adjust the Collection Output / response=collection requirements with improved handling for ambiguous cases mentioned in:
  RFC Part 1 Core v2: Per-output Collection Outputs? #615

  • Added the "multi-output-grouped" case that consist of response=collection when selected outputs is >1. This was not covered an ambiguous. Now it is described with minimal guidance.
  • Added profiles for "results" vs "grouped" collection multi-output, so a client negotiating that request can ask for a specific pattern and validate it go the right result.

• Adjust the dataClasses text (with example 😉) of it potential application

  • I've adjusted some wording that seemed contradictory. In one place it said dataClass outputs were "allOf" applicable, while inputs where "oneOf".
  • Added the hability to include dataClasses in the actual input values/link/collection and output results so semantic details can be reflected in job results (and nested processes chaining them by inheritance)
  • The provided details tie in nicely with ongoing metadata/profiling discussions and OSPD work.
  • Add a reference to the prof:Profile for more context
    @rob-metalinkage FYI

• Collection Filtering

  • I've added the missing assets text.
  • Worked the headers to be referencable.

@pvretano @jerstlouis @gfenoy Let me know what you think.

Notes

I recommend merging #634 before this so I can double check the inconherent header labels / fix conflicts without having massive diffs here.