🚸(frontend) prioritize UI reactivity over error handling in track toggle

Update track muting/unmuting to prioritize immediate UI state changes
over error handling to prevent weird UX delays.

Ensures toggle buttons reflect new state instantly rather than waiting
for operation completion. Users expect immediate visual feedback when
interacting with mute controls, even if errors occur later.

src/frontend/src/features/rooms/components/join/ToggleDevice.tsx

@@ -49,13 +49,13 @@ export const ToggleDevice = <T extends ToggleSource>({
     }
     try {
       if (isTrackEnabled) {
-        await track.mute()
         setIsTrackEnabled(false)
         onChange?.(false, true)
+        await track.mute()
       } else {
-        await track.unmute()
         setIsTrackEnabled(true)
         onChange?.(true, true)
+        await track.unmute()
       }
     } catch (error) {
       console.error('Failed to toggle track:', error)