Action button issues and improvements

Hello,

I can see many small issues or potential improvements related to action buttons.

Here are some of them:

• askConfirmation() is not working in combination with renderAsButton() (used to submit form).

• Some styles are not really rendering well. Eg: asInfoAction() in dark mode or asTextLink() in light mode

• In dark mode, the hover effect of secondary buttons (default when no asXxxAction() style is specified) looks strange. The button briefly flashes white before returning to its normal color.

Batch actions

• askConfirmation() does not work inside BatchAction.
  Instead, we are supposed to use askConfirmationOnBatchActions(), but this method is only available at Crud configuration level, so there is no way to configure a different message par button inside batch actions.
  => Why not just supporting the existing askConfirmation() in batch actions?

• In batch actions, button priority is handled differently from normal views.
  For example, a button using asPrimaryAction() is rendered on the left in the batch action menu, while in the normal view it is rendered on the right.

• For batch actions, add a way to conditionally enable or disable the action button based on the selected items, using displayIf() or a dedicated method.
  For example: an "Archive" batch action should only be enabled if all selected items are in the "completed" status.
  This could be implemented by evaluating the condition for each row and adding a data attribute indicating whether the batch action is allowed for that item, for example data-ea-batch-action-archive="true".

• Unable to use ActionGroup inside batch actions

Start with the action confirmation and batch action documentation linked in the issue, then inspect the existing action and ActionGroup entry points for normal and batch views. The work is done when the listed confirmation, styling, priority, conditional-enabling, and ActionGroup cases are resolved and their behavior is covered consistently.