sway: drop -t 2000/-t 3000 from notify-send, source restore-wayland-env in toggle-dropdown/wifi-menu

The actual cause of 'caffeine notification doesn't show' was the
-t 2000 timeout: the notification popped for 2 seconds and self-cleared
before the user could see it. Manual notify-send from a terminal (no
-t flag) used mako's default-timeout=5000 and was visible — so the user
saw my test notifications but not their own clicks.

Fix: drop the -t flag everywhere so mako config owns the duration.
Added: source restore-wayland-env.sh in toggle-dropdown.sh and
wifi-menu.sh — same env-loss pattern as caffeine.sh, would have
been next on the bug list.

Verified on tadbit: -t 2000 notification visible at +0.5s, gone at
+2.5s (user missed it). No -t flag: visible at +0.5s, gone at +5.5s
(visible long enough to read).

dot_config/sway/caffeine.sh

@@ -30,10 +30,14 @@ if [ -f "$FLAG" ]; then
     rm -f "$FLAG"
     killall swayidle 2>/dev/null
     "$HOME/.config/sway/start-swayidle.sh" &
-    notify-send -t 2000 "☕ Caffeine OFF" "Idle sleep enabled" 2>/dev/null
+    # No -t flag → mako's `default-timeout` (currently 5000ms) controls duration.
+    # Earlier this used -t 2000 (2 seconds) but that vanished faster than the
+    # user could see it — the click "appeared to do nothing" because the
+    # notification popped and self-cleared in 2s. mako config owns the timeout.
+    notify-send "☕ Caffeine OFF" "Idle sleep enabled" 2>/dev/null
 else
     # Turn ON caffeine — kill swayidle
     touch "$FLAG"
     killall swayidle 2>/dev/null
-    notify-send -t 2000 "☕ Caffeine ON" "Idle sleep disabled" 2>/dev/null
+    notify-send "☕ Caffeine ON" "Idle sleep disabled" 2>/dev/null
 fi