Support custom documentation path in doc-style and doc-build actions

[thesct22]

Description

The doc-style and doc-build actions currently hardcode doc/ at the repository root in multiple places, making them incompatible with projects that have documentation in a subdirectory (e.g., blueprint/doc/, src/doc/).

doc-style

While vale-config and files inputs are configurable, the vocabulary directory validation step hardcodes ./doc/styles/config/vocabularies:

if [ ! -d ./doc/styles/config/vocabularies ]; then
    echo "Projects using Vale >=v3 require a doc/styles/config/vocabularies directory."
    exit 1
fi

Proposed fix

Use the files input (or a new doc-path input) to resolve the vocabulary directory path instead of hardcoding ./doc/styles/....

doc-build / _doc-build-linux

Multiple hardcoded doc/ references in _doc-build-linux/action.yml:

• make -C doc html / make -C doc pdf / make -C doc linkcheck
• EXPECTED_BUILD_DIR=doc/_build
• path: doc/_build/html (artifact upload)
• path: doc/_build/latex/*.pdf (artifact upload)

Same issue in _doc-build-windows/action.yml with cd doc.

Proposed fix

Add a doc-path input (default: doc) and use it in place of all hardcoded doc/ references.

Current workaround

Projects with non-standard doc paths must create a symlink before calling the actions:

- run: ln -s blueprint/doc doc
- uses: ansys/actions/doc-style@v10
  with:
    checkout: false
    vale-config: doc/.vale.ini
    files: doc/source

This works but is fragile and non-obvious.

[RobPasMue]

Hi @thesct22 - this request might have larger implications (not only these 2 PRs). Most of our doc-related actions work under the assumption that the documentation is living under a doc folder at the root level of the repository. I am open to the input change if desired but it might not be as trivial as it seems (in the sense that we might have to modify more actions)