Rename `tm_gtsummary` to `tm_tbl_roche_summary`

[donyunardi]

I learned that there are two main functions in Crane that we use: tbl_roche_summary for tables and tbl_listing for listings.

I think we will eventually need to support both of these functions.

If tm_gtsummary currently runs tbl_roche_summary under the hood, what should we call the module that supports tbl_listing?

It seems more straightforward to rename tm_gtsummary to tm_tbl_roche_summary, and then later introduce tm_tbl_listing.

[averissimo]

Sounds good!

To avoid redundant code we can refactor current module to accept a function, let it be gtsummary::tbl_summary or crane::tbl_roche_summary, crane::tbl_listing or xx::xx

The naming being used might be improved to better match the underlying calls, looking more deeply maybe tm_gtsummary shouldn't be exported or just become this "generic function"

[donyunardi]

I like this approach @averissimo, we need to prioritize this issue.

In addition, let's also use teal.picks for this refactor.