feat(button): update button topics

[Hristo313]

Closes #490

Update the button xplat topics

Also updated the samples:
Angular -> IgniteUI/igniteui-angular-samples#4019
React -> IgniteUI/igniteui-react-examples#1097
WC -> IgniteUI/igniteui-wc-examples#1244
Blazor -> IgniteUI/igniteui-blazor-examples#1297

Checklist:

• check topic's TOC/menu and paragraph headings
• Include TOC topic labels in the topic content when it has a valuable update, is new, or is considered preview / beta
• link to other topics using ./page.mdx or ../relative/path.mdx (.mdx extension required)
• at the References section at the end of the topic add links to topics, samples, etc
• reference API documentation instead of adding a section with API

• use valid component names - [Data] Grid, IgxSelectComponent, <igx-combo>
• use spell checker tool (VS Code, Grammarly, Microsoft Editor)
• add inline code blocks for the names of classes / tags / properties
• add language descriptor for the code blocks
• check if links function by running the check-api/mdx npm commands
• check if sample is working and fully visible in the topic
• check if sample is working and fully visible in the StackBlitz
• check if code blocks match the code in StackBlitz demo
• add or update meaningful llms.description metadata and run npm run check:llms-metadata

• follow SEO guidelines to fill topic's metadata (SEO guidelines)

• do not resolve requested changes (leave that to the reviewer)

[DiLazarova]

Button Topic Review

Layout Template Section

For this layout example

use the one we have in our design documentation to show the button with and without the icon

instead of contained button variant, please use "Outlined".

For the Size section please use the example from the Design File in Figma: Figma File

For Style Parts Section please check again the hover states to have a good contrast:

[ChronosSF]

there is no button package, also the theme package has a different release cadence . A WC release will depend on a certain igniteui-theming version and won't work well without an update (same for the other platforms), but generally speaking since the theming package is a dep, the user doesn't really have to do anything to have them . I am not sold on the value this section provides tbh.

[ChronosSF]

The react and wc sections can be combined as there is a {} template token for the react package too.

[ChronosSF]

You are talking about importing the directive but import the module which is a deprecated thing for backwards compatibility for people using modules instead of stand-alone. We don't want to do that, just import the directive.

[ChronosSF]

erm, shouldn't we be using the platform-specific wrapper element - igrButton, igbButton etc?

[ChronosSF]

here only Idle is bolded, while the other states are not