docs: rewrite button syling docs to mention Aura

[web-padawan]

• Moved "Style variants" examples from the Button page to Styling tab
• Updated custom CSS properties tables to mention Lumo / Aura support
• Created a table to list variants Lumo / Aura support & Aura selectors

[rolfsmeds]

We should probably rework the variants docs at some point to be a bit more compact, but that needs a lot of thinking and can be left for later. Good enough for now, let's just change the caption of the selector column.

[sissbruecker]

For Button this table structure makes sense, and it's mostly obvious what the individual variants do. However for other components it would be very valuable to have a description on what a variant does, especially since Aura specific theme variants don't have separate section / example.

Also the selector column makes less sense for other components, since variants there probably always use the theme attribute. Or are there other components where you use a class name?

So maybe we should rather have a description column, and then specifically for Button have some additional paragraph that Aura requires applying class names for success / warning / error instead of the theme attribute?

[web-padawan]

Makes sense, thanks. Added the "description" column with the usage recommendation (text mostly copied from below with some slight adjustments) and a "note" admonition regarding Aura CSS class names.

[sissbruecker]

Nit: Could unify the order in which Aura and Lumo are listed.

[web-padawan]

Thanks, done.

[github-actions]

AI Language Review

The updated documentation consolidates information well but has removed sections that provided a more comprehensive understanding of button styles and their usage. Below are some issues and suggestions:

1. Removed Section on Styles:

   • The new version omits detailed sections on styles such as Danger, Warning, and Size Variants. Consider restoring these details as they help users understand when and why to use certain styles.

2. Removed Example Tables:

   • The new documentation has removed tables that provided a quick reference for style variants and their recommendations. Consider reintroducing these tables for easy reference, maintaining usability for developers needing quick guidance.

3. Footnotes for Special Cases:

   • The previous document mentioned that certain combinations, like "Tertiary + Contrast," should be avoided due to their similarity to non-interactive text. This information is crucial for preventing design issues and should be included.

4. Focus on Theming:

   • The focus is heavily on textual descriptions rather than visual examples in the new version. Consider including more examples or visual aids directly related to the themes discussed, which could enhance comprehension.

By addressing these points, you can enhance the clarity and usefulness of the Button documentation for users, ensuring it provides both comprehensive information and quick, accessible insights.

The comment has been addressed and the variants table is updated.