feat(processor): append @example tags to member description body #5

[Katari-8055]

Closes #5

Summary

This PR improves the visibility of code examples in the generated documentation by moving @example block tags into the main reflection body (summary). By appending these examples directly to the reflection's primary description during the processing phase, we ensure they are always rendered in the final output, even when the theme is configured to hide standard block tags. This ensures that usage examples are always accessible to developers without requiring changes to the theme's core visibility settings.

What kind of change does this PR introduce?

feat (feature for the documentation processor)

Did you add tests for your changes?

The changes were manually verified by adding a demo @example tag in webpack/types.d.ts, running npm run generate-docs, and confirming that the example appeared in the generated .md files inside the pages/v5.x directory.

Does this PR introduce a breaking change?

No.

If relevant, what needs to be documented once your changes are merged or what have you already documented?

No external documentation is required. This change automatically enhances how existing and future @example JSDoc tags are rendered in the Markdown output.

Use of AI

Yes, for research purpose !

[avivkeller]

This belongs in the theme, not the processor

[Katari-8055]

This belongs in the theme, not the processor

Thanks for the clarification! That makes sense. I'll move the implementation to the theme instead of the processor and push an update shortly.