Remove set_datanames functionality

[donyunardi]

Continuation of #1380 (comment)

Summary

We will remove the set_datanames functionality from the codebase and update a handful of teal modules to ensure users can control the module's datanames from the module's constructor.

While most modules include an argument (or equivalent to it) to configure datanames, some do not:

Definition of Done

• Remove the set_datanames feature from the codebase, including related unit tests and associated components.
• Allow users to set datanames in the module's constructor in teal.modules.general.
• Allow users to set datanames in the module's constructor in teal.modules.clinical.

We have identified the teal modules affected in teal.modules.general (TMG) and teal.modules.clinical (TMC), and we will open issues for these modules.

Our priority will be to address the modules in tmc and tmg first. Other non-CRAN-released teal modules, such as teal.osprey and teal.goshawk, will be addressed at a later stage.

Tasks

• Remove the set_datanames feature from the codebase #1437
• Ability to set datanames in module's constructor teal.modules.general#821
• Ability to set datanames in module's constructor teal.modules.clinical#1307