Update settings toggles to use consistent design across app.

[Half-Shot]

Needs element-hq/compound-web#358

This PR effectively changes all the various places we expose a ToggleSwitch (or a handful of places we used a checkbox) to use a standard SettingsToggle switch that always keeps the settings toggle to the left of the label, which provides the best accessibility. This also ensures that all toggles have their descriptions and disabled messages where possible.

This PR is absolutely enormous (sorry!!!!) due to the number of places require to change, so to break the changes down further the following things have been changed:

• All areas of Element with a toggle switch, which do not have playwright tests, now have playwright tests.
• Some playwright/jest tests have been adjusted to use the "switch" role, rather than "checkbox" or other less-ideal ways to identify a setting switch.
• Some areas of Element, such as the legacy settings panel did not use our SettingsFlag component where they could trivially include it. This has been fixed.
• LabelledToggleSwitch has been removed in favour of Compound's SettingsToggle
• Due to Radix inputs (from Compouund) requiring components be wrapped in Forms, a careful dance of wrapping aspects of the settings components in forms has been performed.

I'd suggest reviewing by checking the code changes first, then jest, then playwright changes in that order which will make the most sense. While the PR is huge, the majority of the trivial changes are component swicheroos or screenshot tests.

Changes areas with screenshot test:

• ApperanceTab
• CreateRoomDialog
• DeclineInviteDialog
• DevToolsDialog
• ReportRoomDialog
• RoomUpgradeWarningDialog
• WidgetCapabilitiesPromptDialog
• WidgetOpenIDPermissionsDialog
  • Looks hard to actually prompt, maybe skip?
• EnableLiveShare
• General Room Tab
• Notifications
• NotificationSettings (new)
• SecurityTab
• RoomSecurityTab
• VoipRoomSettingsTab
• PreferencesTab
• VoiceUserSettingsTab
• SpaceSettingsVisibilityTab

Checklist

• Tests written for new code (and old code if feasible).
• New or updated public/exported symbols have accurate TSDoc documentation.
• Linter and other CI checks pass.
• I have licensed the changes to Element by completing the Contributor License Agreement (CLA)

[t3chguy]

Suggesting this skips sonar given most of the untested code is the mostly-unused onSubmit prevent default on the Compound Form Roots which in many cases is not reachable but still worthwhile going forward in case more traditional form elements are used at any point later, and needed to satisfy the type and there are a lot of end to end tests covering these changes.