[Toggle button] Implement in code

[emirgens]

Summary

Implement component in code, using the agreed workflow, with component-owned CSS typography from the start.

Acceptance Criteria

• All variants implemented (e.g. size, emphasis, state, icon/no icon, etc.)
• Pull Request review and approved

[claude]

These existing issues look related to this one and may be worth a look before starting:

• [Toggle button] Upgrade to align with EDS foundations and accessibility standards #5342 — [Toggle button] Upgrade to align with EDS foundations and accessibility standards (open): the parent/epic task for the Toggle button upgrade, whose acceptance criteria list this implementation as one of its sub-tasks.
• [Toggle button] Update design in Figma #5343 — [Toggle button] Update design in Figma (open): the sibling design task that defines the variants, states and token mappings this code implementation should follow 1:1.
• Add toggle buttons to new EDS #5327 — Add toggle buttons to new EDS (open): a consumer feature request for toggle buttons in the new EDS (used in Echo), with screenshots of real usage that can inform the required variants.
• Toggle Button #2450 — Toggle Button (closed as completed): the original Toggle button work, including variant research and the accessibility requirements (role="group", aria-pressed, keyboard behaviour) that still apply to the new implementation.

This comment was generated by an LLM and may be inaccurate. Please verify that the linked issues are actually relevant.