fix(e2e): consolidate specs into single file and fix WebDriver click issues

Tauri creates one app session per spec file; multiple files caused
invalid session id on subsequent specs. WebDriver clicks on Svelte 5
components inside scrollable panels dont trigger onclick handlers
via WebKit2GTK/tauri-driver - use browser.execute() JS clicks.
Also removed tauri-plugin-log (redundant with telemetry::init()).

v2/src-tauri/Cargo.toml

@@ -22,7 +22,6 @@ serde_json = "1.0"
 serde = { version = "1.0", features = ["derive"] }
 log = "0.4"
 tauri = { version = "2.10.3", features = [] }
-tauri-plugin-log = "2"
 rusqlite = { version = "0.31", features = ["bundled"] }
 dirs = "5"
 notify = { version = "6", features = ["macos_fsevent"] }

v2/src-tauri/src/lib.rs

@@ -621,14 +621,10 @@ pub fn run() {
         .plugin(tauri_plugin_updater::Builder::new().build())
         .plugin(tauri_plugin_dialog::init())
         .setup(move |app| {
-            if cfg!(debug_assertions) {
-                // Ignore error if logger already initialized (telemetry::init sets up tracing-subscriber)
-                let _ = app.handle().plugin(
-                    tauri_plugin_log::Builder::default()
-                        .level(log::LevelFilter::Info)
-                        .build(),
-                );
-            }
+            // Note: tauri-plugin-log is NOT initialized here because telemetry::init()
+            // already sets up tracing-subscriber (which bridges the `log` crate via
+            // tracing's compatibility layer). Adding plugin-log would panic with
+            // "attempted to set a logger after the logging system was already initialized".
 
             // Create TauriEventSink for core managers
             let sink: Arc<dyn bterminal_core::event::EventSink> =