Implement more actions for columns

[DivadNojnarg]

Will fix #19

[DivadNojnarg]

@olajoke A working prototype for implementing MenuColumn:

library(shiny)
library(bslib)
library(palmerpenguins)

ui <- page_fluid(
  cheetahR::cheetahOutput("table")
)

server <- function(input, output, session) {
  output$table <- renderCheetah({
    cheetah(
      penguins
    )
  })
}

shinyApp(ui, server)

[olajoke]

@DivadNojnarg Interestingly, I have addressed this same issue in a separate branch (see here). While your approach dynamically applies menuColumn to detected factor columns, mine lets users provide the label/value list directly. Merging our approaches could offer more flexibility. Let's discuss it further tomorrow.

[DivadNojnarg]

@olajoke Few comments when I was checking the API:

• I've seen that Cheetah allows to create a readonly Dropdown menu that does not open (https://future-architect.github.io/cheetah-grid/documents/api/js/column_types/MenuColumn.html). I wonder what is the interest. The dropdown is only of interest when it can be opened. We'd have to account for this.
• In general, we can pass column type as a string like check, ... However, many example actually use the JS constructors for each type like (to provide more flexibility):

columnType: new cheetahGrid.columns.type.NumberColumn({
        format: new Intl.NumberFormat("en-US", {
          style: "currency",
          currency: "USD",
        }),
      }),

• For actions, same comment, we can pass input for a text field but also we can call SmallDialogInputEditor https://future-architect.github.io/cheetah-grid/documents/api/js/column_actions/SmallDialogInputEditor.html to have more flexibility like having a validator:

action: new cheetahGrid.columns.action.SmallDialogInputEditor({
        classList: "helper-text--right-justified",
        helperText(value) {
          return `${value.length}/20`;
        },
        inputValidator(value) {
          return value.length > 20
            ? `over the max length. ${value.length}`
            : null;
        },
        validator(value) {
          return value.match(/^[a-zA-Z]*$/) ? null : "Please only alphabet.";
        },
      })

Our refactoring should account for that.