logiguard fork: add Window::activate_with_token for externally-minted xdg-activation tokens

Mutter honors xdg_activation_v1.activate() only when the token carries a
valid grab serial on the surface being activated. activate_window() mints
its own token using this client's KeyboardEnter serial, which is stale
after a tray-menu click (the tray popup held focus, not the app window).

Add Window::activate_with_token(&str) so callers can feed in a token
minted by GTK (via g_app_launch_context_get_startup_notify_id) on the
connection that actually received the user gesture. That token carries
the real grab serial + focused surface, which Mutter accepts.

- crates/gpui/src/platform.rs: PlatformWindow::activate_with_token with
  default impl that falls back to activate().
- crates/gpui/src/window.rs: public Window::activate_with_token.
- crates/gpui_linux/src/linux/wayland/window.rs: WaylandWindow impl that
  issues xdg_activation_v1.activate(token, surface) directly.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

crates/gpui/src/platform.rs

@@ -623,6 +623,16 @@ pub trait PlatformWindow: HasWindowHandle + HasDisplayHandle {
         answers: &[PromptButton],
     ) -> Option<oneshot::Receiver<usize>>;
     fn activate(&self);
+    /// Activate with an externally-generated xdg-activation token.
+    /// Wayland: issues `xdg_activation_v1.activate(token, surface)` directly,
+    ///   bypassing this client's own (possibly stale) serial. The caller is
+    ///   responsible for obtaining a token that carries a valid grab serial —
+    ///   e.g. from GTK's `GdkAppLaunchContext::startup_notify_id()` on the
+    ///   connection that received the user gesture.
+    /// Non-Wayland backends: ignore the token and fall back to `activate()`.
+    fn activate_with_token(&self, _token: &str) {
+        self.activate();
+    }
     fn is_active(&self) -> bool;
     fn is_hovered(&self) -> bool;
     fn background_appearance(&self) -> WindowBackgroundAppearance;