feat(switch): update switch topics

[Hristo313]

Closes #537

Update the switch xplat topics

Also updated the samples:
Angular -> IgniteUI/igniteui-angular-samples#4025
React -> IgniteUI/igniteui-react-examples#1102
WC -> IgniteUI/igniteui-wc-examples#1254
Blazor -> IgniteUI/igniteui-blazor-examples#1302

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)

[ChronosSF]

I don't know what that Form is... This needs a link or an elaboration. My guess is that it's actually a Blazor only note.

[ChronosSF]

@Hristo313 , I don't see the note about using Form instead of <form> in the doc anymore, I hope you checked and it's indeed no longer relevant.

[Hristo313]

The warning is now scoped to Blazor only. In Blazor we should use EditForm instead of the standard HTML

element.

[ChronosSF]

I think both the Angular and the non-angular platform block under this one show the exact same content and can be combined .

[ChronosSF]

This is similar to the previous comment. It seems that you are platformblock-ing the same text for Angular vs the Rest. I am not sure if this is hallucination on the agent side but it makes the document needlessly complicated.

If you are doing it because of issues with the ApiLink then those need to be fixed instead. (also you can just platformblock inline just the apilink as an interim solution.

[ChronosSF]

Same text between Angular and the rest - same comment as above