docs: document multiple-file Vale input for doc-style

[jorgepiloto]

This updates the doc-style action docs to show how to lint an explicit list of files with Vale.

• Clarifies that the files input accepts either a directory path or a JSON-formatted array of file paths.
• Adds a doc-style-multiple-files.yml example that builds a JSON file list with jq and passes it through env.VALE_FILES.

Closes #730.

[github-actions]

The documentation for this pull request will be available at https://actions.docs.ansys.com/pull/1501. Please allow some time for the documentation to be deployed.

[RobPasMue]

Nice example!

[moe-ad]

Thanks for this @jorgepiloto. I left a few comments.

Also can we test this just to make sure it works? I know we have faced issues in the past concerning passing json-formatted data to nested action calls. We can simply extend the existing ci test as a minimum.

[moe-ad]

I am requesting changes just to make sure we don't mistakenly merge given the existing approvals.

[jorgepiloto]

Thanks for the suggestions, @moe-ad. Feel free to merge when CI/CD passes.

[SMoraisAnsys]

For consistency, could you refactor this step to use shell: python instead ? That's how we are handling that in other actions.

[moe-ad]

Doable, yes. But that approach will make writing to GITHUB_OUTPUT not as straightforward as just doing it through bash. So I would advice leaving it as is.

[SMoraisAnsys]

Feel free to discard my comment then but I would emphasize to improve consistency in other actions then.

Note that, AFAIK, moving to shell: python would only require to replace print(f"vale_files={json.dumps(files)}") with

    with open(os.environ["GITHUB_OUTPUT"], "a") as f:
        f.write(f"vale_files={json.dumps(files)}\n")

But again, as long as we are consitent, I'm fine with it.