Adding more text for exclusive vs inclusive parameters and added diagram

[acoleman2000]

This pull request is based on this issue.

Add clarifying information about exclusive vs inclusive parameters, as well as including a diagram to illustrate the difference.

Upfront described how cwltool handles exclusive vs inclusive parameters, so user can follow along better with examples.

[kinow]

The rendered HTML with the image and the new text are looking great! Left some comments about the markdown text.

The RTD build is failing. I tried to have a look but couldn't understand what's going on, so I'll revisit it later.

Traceback (most recent call last):
  File "/home/docs/checkouts/readthedocs.org/user_builds/common-workflow-languageuser-guide/envs/384/lib/python3.9/site-packages/sphinx/config.py", line 350, in eval_config_file
    exec(code, namespace)
  File "/home/docs/checkouts/readthedocs.org/user_builds/common-workflow-languageuser-guide/checkouts/384/src/conf.py", line 257, in <module>
    from myst_parser.mdit_to_docutils.sphinx_ import SphinxRenderer, create_warning
ImportError: cannot import name 'create_warning' from 'myst_parser.mdit_to_docutils.sphinx_' (/home/docs/checkouts/readthedocs.org/user_builds/common-workflow-languageuser-guide/envs/384/lib/python3.9/site-packages/myst_parser/mdit_to_docutils/sphinx_.py)

Re-ran the build on RTD, but it failed the same way.

Thanks!
Bruno

[kinow]

In other pages & paragraphs cwltool appears formatted as cwltool (the command). We should probably use that here too for consistency (although I noticed there are some places where it's written without the formatting).

[kinow]

Probably better to break this line to make it shorter like the other ones (regardless of 80 or 120 limits).

This is useful to visualize diffs with git or GitHub UI: https://sembr.org/

[kinow]

I think the extra blank lines are not necessary. This is not really important, but we tried to remove unnecessary blank lines before, so probably better if we can avoid adding extra lines that are not necessary.

[zoe-translates]

Thank you @acoleman2000 for this!

One more thing I noticed while doing the translation work in this section.

Here we have the word "inclusive" in the section subtitle. That's the only place this word appears in this section (without this PR). It appears to me that the word was being used interchangeably with "dependent". The term "dependent is used in the FAQ, where "inclusive" doesn't appear there.

In fact, running ag -iG '^.+\.md$' 'inclusive' in the src directory (i.e. print all occurrence of the word "inclusive" in markdown files), the only hit is this one here.

I think what this means is that we have reason to do away with the word "inclusive" here and replace it with "dependent".

[zoe-translates]

The rendered HTML with the image and the new text are looking great! Left some comments about the markdown text.

The RTD build is failing. I tried to have a look but couldn't understand what's going on, so I'll revisit it later.

Traceback (most recent call last):
  File "/home/docs/checkouts/readthedocs.org/user_builds/common-workflow-languageuser-guide/envs/384/lib/python3.9/site-packages/sphinx/config.py", line 350, in eval_config_file
    exec(code, namespace)
  File "/home/docs/checkouts/readthedocs.org/user_builds/common-workflow-languageuser-guide/checkouts/384/src/conf.py", line 257, in <module>
    from myst_parser.mdit_to_docutils.sphinx_ import SphinxRenderer, create_warning
ImportError: cannot import name 'create_warning' from 'myst_parser.mdit_to_docutils.sphinx_' (/home/docs/checkouts/readthedocs.org/user_builds/common-workflow-languageuser-guide/envs/384/lib/python3.9/site-packages/myst_parser/mdit_to_docutils/sphinx_.py)

This should be fixed by f940a62. A rebase should fix the build error.

[mr-c]

Thanks! Is there a SVG or other vector source for this image?