ARD Function Names

[ddsjoberg]

This was recently reported by user and it's something @bzkrouse and I have also discussed in the past, but haven't actioned on it yet.
https://github.com/insightsengineering/cards/issues/470

We're thinking of updating our primary function names. Below are some ideas we brainstormed.

`ard_categorical()` ▶ `ard_tabulate()`, `ard_freq()`, `ard_count()`, `ard_table()` (perhaps too generic because most people will use all `ard_*()` functions to create summary tables?)
`ard_continuous()` ▶  🤷🏼 (`ard_summary()` but will be confused with `summary()`?, `ard_univariate()`, `ard_uvariate()`)
`ard_complex()` ▶ 🤷🏼 (I have never liked this name. It was a placeholder that never got updated. `ard_mvsummary()`, `ard_mvariate()`)

Our top picks are

`ard_categorical()` ▶ `ard_tabulate()`
`ard_continuous()` ▶ `ard_summary()` The title of the function will include 'Univariate Summaries' to distiguish between the multivariate summaries in `ard_complex()
`ard_complex()` ▶ `ard_mvsummary()`
`ard_dichomous()`  ▶ `ard_tabulate(values)` where you specify the value/level you want returned

But we'd love to hear your thoughts as well!
@malanbos @kimjj93 @jtalboys @daniel-woodie @ayogasekaram @edelarua @Melkiades

[ayogasekaram]

I like the top pick selections! I think ard_mvsummary is different enough to avoid confusion with ard_summary

[edelarua]

I agree!! All of the changes sound good to me

[Melkiades]

maybe ard_summary_mv()? and ard_tabulate2()? For the rest is fine with me. Never had big issues with the other definitions neither (only complex I would change into ard_continuous_mv())