Adds decorators to tm_t_pp_basic_info

[averissimo]

Part of insightsengineering/teal#1371

Working example

# Load packages
pkgload::load_all("../teal.modules.clinical", export_all = FALSE)
# Example below

insert_rlisting_footer_decorator <- function(default_caption = "I am a good new footer", .var_to_replace = "table") {
  teal_transform_module(
    label = "New row",
    ui = function(id) shiny::textInput(shiny::NS(id, "new_footer"), "New footer", value = default_caption),
    server = make_teal_transform_server(
      substitute({
        rlistings::main_footer(.var_to_replace) <- new_footer
      }, env = list(.var_to_replace = as.name(.var_to_replace)))
    )
  )
}

data <- teal_data()
data <- within(data, {
  ADSL <- tmc_ex_adsl
})
join_keys(data) <- default_cdisc_join_keys[names(data)]

ADSL <- data[["ADSL"]]

init(
  data = data,
  modules = modules(
    tm_t_pp_basic_info(
      label = "Basic Info",
      dataname = "ADSL",
      patient_col = "USUBJID",
      vars = choices_selected(choices = variable_choices(ADSL), selected = c("ARM", "AGE", "SEX", "COUNTRY", "RACE", "EOSSTT")),
      decorators = list(
        table = insert_rlisting_footer_decorator(.var_to_replace = "table")
      )
    )
  )
) |> shiny::runApp()

[llrs-roche]

I see you moved some options from the module to the template function. I think this is to make it easier to have a decorator on the interactive table of the shiny app and one for the static on the reporter.
My only concern with this approach is that the dt_decorator is quite complex (suppose because it cannot use make_teal_transform_server) and I thought that we would only decorate objects that end up on the reporter. Perhaps we can talk about it

[llrs-roche]

After checking with the team I was reminded that we are only adding decorators for objects that are on the reporters. Changes to the table_dt (not used on the reporter) should be reverted.