CI: remove potential vale warnings

[SMoraisAnsys]

At least since version 2.29.3 of vale, titles are also checked by vale. Thus, multiple warning started appearing due to non deterministic behavior when using multiple (differently-cased) entries for the same terme.

The proposed solution consists in reworking the accept.txt file until no more warnings are generated.

[ansys-reviewer-bot]

Thanks for opening a Pull Request. If you want to perform a review write a comment saying:

@ansys-reviewer-bot review

[Samuelopez-ansys]

Great!

[codecov]

Codecov Report

Merging #3806 (c911c0e) into main (7eae896) will increase coverage by 0.02%.
Report is 4 commits behind head on main.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #3806      +/-   ##
==========================================
+ Coverage   81.08%   81.10%   +0.02%     
==========================================
  Files         180      180              
  Lines       62140    62225      +85     
==========================================
+ Hits        50384    50468      +84     
- Misses      11756    11757       +1     

[Samuelopez-ansys]

@SMoraisAnsys Is this PR still a draft?

[SMoraisAnsys]

@SMoraisAnsys Is this PR still a draft?

Yes, I would like to be sure that everything is working as expected.

[SMoraisAnsys]

I think the changes are working. Since I was not able to get any error, I added some strange sentence in the documentation to trigger vale and only this sentence got caught. Sentence added "Babedibabedibou rofl"

Vale report :

/home/runner/vale --output=/home/runner/work/_actions/errata-ai/vale-action/reviewdog/lib/rdjsonl.tmpl --config=doc/.vale.ini doc
  {"message": "[Vale.Spelling] Did you really mean 'Babedibabedibou'?", "location": {"path": "doc/source/API/Application.rst", "range": {"start": {"line": 31, "column": 1}}}, "severity": "ERROR"}
  {"message": "[Vale.Spelling] Did you really mean 'rofl'?", "location": {"path": "doc/source/API/Application.rst", "range": {"start": {"line": 31, "column": 17}}}, "severity": "ERROR"}

I'll rewrite the history to only keep the changes of interest.
@Samuelopez-ansys Do I change the way the vale work is triggered (either using pyansys action or directly using errata-ai/vale-action@reviewdog) ?

[Samuelopez-ansys]

@SMoraisAnsys Could we merge?