Documentation on module's return

[donyunardi]

Feature description

Now that our module returns something (i.e. reporter card function), we should document this in the manuals/roxygen if the module is reportable.

One proposal is to inherit from a centralize place.

This will need to be done after we finalize the refactor and before we rewrite of the functions.

Code of Conduct

• I agree to follow this project's Code of Conduct.

Contribution Guidelines

• I agree to follow this project's Contribution Guidelines.

Security Policy

• I agree to follow this project's Security Policy.

[m7pr]

Hey @donyunardi @gogonzo @averissimo
I added a section on Reporting to tm_a_pca.R as a concept of what content could be copied around other modules.

I think we should emphesize that module's server returns teal_report and that turns the autoreporting feature. And basically that's it. Later I link to 2 vignettes in teal.

Here is the prototype of the section that we can then reuse in other modules

c956be3

[m7pr]

Just moved this section to teal::example_module
548bb23d74a2b917e67cdacb8fd835ac821de99c
and added the inheritance in tmg modules in
6ab1716