test(docs): add TestClass with all annotations for markdown generation

[frankzengjj]

What changes are being made and why?

closes #7911

Replaces real Task class with a dedicated TestClass that implements all annotations to generate the most complex markdown. This ensures accurate coverage of plugin documentation rendering

---

How the changes have been QAed?

I created a unit test class TestTaskDocumentationTest that generate the markdown and run the test locally. Also, I printed the markdown output and visually inspected it.

---

Setup Instructions

none. Just need to run the test.

[fhussonnois]

Hi @frankzengjj thank you very much for the contribution.

The idea behind the issue is also to replace existing tests from the DocumentationGeneratorTest class.

Could you please :

merge your new class TestTaskDocumentationTest with DocumentationGeneratorTest .
remove existing test methods based on core tasks (e.g., tasks, dags, returnDoc, defaultBool. Set);
also, you need to add some tests for testing deprecated plugins, or properties. For doing that, you can create a new class TestTaskWithDeprecated - for this you can have a look to the existing test DocumentationGeneratorTest#echo.
Thank you

[brian-mulier-p]

Also, @frankzengjj are you using the generated markdowns on your side?
We replaced every usage of it with a json-schema based implementation instead to have proper model and do the design directly in the front-end (doc, in-editor doc, ...) so I think it will be removed somedays so I'm not sure it's worth investing more time on it

[frankzengjj]

Thank you @fhussonnois and @brian-mulier-p for all the feedback and comment I will look into this.

[MilosPaunovic]

Hey @frankzengjj, are there any updates on this?

[loicmathieu]

Closing this PR as we haven't heard back from the contributor for 2 months.
Please don't hesitate to reopen it when all feedback has been taken care of, if you still want to work on it.