Force doc style check with Vale before building the doc

[PProfizi]

Vale had been integrated to the repository but only within a manually triggerable workflow.
This PR calls this workflow in the regular CI as a check step before building the documentation.
https://vale.sh/docs/vale-cli/overview/

Install Vale on Windows using choco (also explains how to install chocolatey):
https://docsy-site.netlify.app/docs/vale/install-vale/
Also install Sphinx using choco (required to treat .rst files):
choco install sphinx

How to integrate it to PyCharm as a tool:
https://vale.sh/docs/integrations/jetbrains/

[codecov]

Codecov Report

Merging #689 (0407368) into master (684d6c5) will increase coverage by 0.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #689      +/-   ##
==========================================
+ Coverage   88.20%   88.23%   +0.02%     
==========================================
  Files          69       69              
  Lines        7760     7760              
==========================================
+ Hits         6845     6847       +2     
+ Misses        915      913       -2     

[PProfizi]

@PipKat @Revathyvenugopal162 I am having Vale errors I do not know how to fix:

• It raises a Google.Spacing error on paths/filenames such as: "And.Dpf.bat" saying there should be a space between d and D...
• It raises a Google.Spacing error for class references such as :class:Model<ansys.dpf.core.model.Model> saying there should be a space between l and M.
  Basically it raises spacing errors as soon as a capital letter follows a period. Do you know how to fix/ignore those?

[PipKat]

@PProfizi You want to tag all file names in literal strings, like this And.Dpf.bat to avoid Vale errors.
For class directives, you want to use :class: followed by the name of the class surrounded by single back ticks. Here is an example of what I mean:

If you'd like, I can check out your branch and resolve all of the Vale errors.

[PProfizi]

@PProfizi You want to tag all file names in literal strings, like this And.Dpf.bat to avoid Vale errors. For class directives, you want to use :class: followed by the name of the class surrounded by single back ticks. Here is an example of what I mean:

If you'd like, I can check out your branch and resolve all of the Vale errors.

Hi @PipKat! Thank you! I've proposed modifications to make the Vale test pass, please tell me if what I did is ok as I am not sure this is the best way to allow for what we want.
Also, I do not know why but I get the errors with :class:... only locally. The GitHub action does not raise them.

[PipKat]

Suggested change

	Running the DPF Server in a Docker container
	~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
	Running DPF Server in a Docker container
	~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
	```Based on the "Getting started with DPF Server" title earlier, it looks like DPF Server is being used like a product name. Consequently, the "the" isn't necessary.

[PipKat]

@PProfizi Is the name of the file Dockerfile? If so, you have written and tagged it correctly. If it is a generic reference, it should be "download the Docker file" with it being two words--a file belonging to or related to Docker.

[PProfizi]

@PipKat yes indeed the file is named Dockerfile

[PipKat]

@PProfizi You want to tag all file names in literal strings, like this And.Dpf.bat to avoid Vale errors. For class directives, you want to use :class: followed by the name of the class surrounded by single back ticks. Here is an example of what I mean:
If you'd like, I can check out your branch and resolve all of the Vale errors.

Hi @PipKat! Thank you! I've proposed modifications to make the Vale test pass, please tell me if what I did is ok as I am not sure this is the best way to allow for what we want. Also, I do not know why but I get the errors with :class:... only locally. The GitHub action does not raise them.

Your changes look good to me! I'm not sure what the :class: directive is only causing issues locally. Perhaps the links can only be built as part of the GitHub workflow?