chore: remove workaround related to url refreshing

With the new API we don't need to generate a new page with a new title (the deployment URL)
so we can remove the existing workaround that triggered a redraw of the new UI page.

Author: fioan89

src/main/kotlin/com/coder/toolbox/CoderToolboxContext.kt

@@ -3,7 +3,6 @@ package com.coder.toolbox
 import com.coder.toolbox.store.CoderSecretsStore
 import com.coder.toolbox.store.CoderSettingsStore
 import com.coder.toolbox.util.toURL
-import com.coder.toolbox.views.CoderPage
 import com.jetbrains.toolbox.api.core.diagnostics.Logger
 import com.jetbrains.toolbox.api.core.os.LocalDesktopManager
 import com.jetbrains.toolbox.api.localization.LocalizableStringFactory
@@ -14,10 +13,8 @@ import com.jetbrains.toolbox.api.remoteDev.states.EnvironmentStateColorPalette
 import com.jetbrains.toolbox.api.remoteDev.ui.EnvironmentUiPageManager
 import com.jetbrains.toolbox.api.ui.ToolboxUi
 import kotlinx.coroutines.CoroutineScope
-import kotlinx.coroutines.delay
 import java.net.URL
 import java.util.UUID
-import kotlin.time.Duration.Companion.milliseconds
 
 @Suppress("UnstableApiUsage")
 data class CoderToolboxContext(
@@ -91,26 +88,4 @@ data class CoderToolboxContext(
             i18n.ptrl("OK")
         )
     }
-
-    /**
-     * Forces the title bar on the main page to be refreshed
-     */
-    suspend fun refreshMainPage() {
-        // the url/title on the main page is only refreshed if
-        // we're navigating to the main env page from another page.
-        // If TBX is already on the main page the title is not refreshed
-        // hence we force a navigation from a blank page.
-        ui.showUiPage(CoderPage.emptyPage(this))
-
-
-        // Toolbox uses an internal shared flow with a buffer of 4 items and a DROP_OLDEST strategy.
-        // Both showUiPage and showPluginEnvironmentsPage send events to this flow.
-        // If we emit two events back-to-back, the first one often gets dropped and only the second is shown.
-        // To reduce this risk, we add a small delay to let the UI coroutine process the first event.
-        // Simply yielding the coroutine isn't reliable, especially right after Toolbox starts via URI handling.
-        // Based on my testing, a 5–10 ms delay is enough to ensure the blank page is processed,
-        // while still short enough to be invisible to users.
-        delay(10.milliseconds)
-        envPageManager.showPluginEnvironmentsPage()
-    }
 }

src/main/kotlin/com/coder/toolbox/util/CoderProtocolHandler.kt

@@ -72,7 +72,7 @@ open class CoderProtocolHandler(
         try {
             markAsBusy()
             reInitialize(restClient, cli)
-            context.refreshMainPage()
+            context.envPageManager.showPluginEnvironmentsPage()
             if (!prepareWorkspace(workspace, restClient, workspaceName, deploymentURL)) return
             // we resolve the agent after the workspace is started otherwise we can get misleading
             // errors like: no agent available while workspace is starting or stopping