With the new TBX API we can update the title of a UI page
without recreating the page and using hacks to force TBX
to update the internal state.

Used by the Toolbox 2.7

We still need to switch from the coder setup page back to the main screen
once the coder cli and the rest api poller is initialized.

Similar with the initial setup page we can use the new TBX API to
update the title of the uri handling page without recreating it and using
hacks to force TBX to update the internal state.

TBX 2.7 API prioritizes connection status to the remote TBX agent over
the workspace status. This would mean that a running workspace would be
listed as disconnected instead of ready. This is confusing as it only
happens for running workspaces and on top of that we also have a green
badge that is rendered by TBX when the agent connection is established.

A new API was added to allow proxy authentication

The new TBX 2.7 API allows us to change the message displayed
while loading the workspaces from "Loading environments" to
"Loading workspaces"

The new TBX 2.7 api exposes basic auth credentials for proxy.

The new API introduced in TBX 2.7, and HTTP proxy authentication works flawlessly. However,
SOCKS5 proxy authentication does not appear to be properly supported in the current TBX
implementation.

While users can configure a SOCKS5 proxy with basic authentication, Toolbox fails to
authenticate successfully. Coder uses OkHttp as the HTTP client, which in turn delegates
SOCKS5 authentication to the JVM (java.net.SocksSocketImpl). We can configure a java.net
.Authenticator with the credentials exposed by the new TBX API. However, since the
Authenticator is set globally, doing so would affect all plugins — including TBX itself —
which may not be desirable.

Introduces support for Toolbox 2.7

Toolbox 2.7 came with small upgrades for kotlin, coroutines and
the serialization library. This PR stays in sync.

A new Toolbox 2.7 build is available with newer API

The IDE resolution can start before the workspace are polled
and the remote provider is initialized. This commit waits for
the first poll to run before continuing to installing and launching
the IDE. Otherwise, Toolbox will raise an error that the env. does not exist.

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.

Toolbox 2.7 provides support plugin aliasing in the URI
as part of https://youtrack.jetbrains.com/issue/TBX-14481

Toolbox 2.7 allows the ide to open paths (via uri handling) on the remote that
were not previously a proper IDEA project.

There is a minor issue that I raised in https://youtrack.jetbrains.com/issue/TBX-14952/ with
paths that point out to folders or files that do not exist. In this case, TBX pops up a dialog
saying "Connecting to remote host..."  and it stays like that forever.

In previous TBX versions (2.6 and before) there was no progress while establishing the SSH
connection, which is why we added a custom "SSHing" label with a circular progress bar while
connecting to the SSH. While providing feedback to https://youtrack.jetbrains.com/issue/TBX-14925 I've noticed that TBX no longer renders "SSHing..", instead we have a "Connecting" label. This is apparently a new feature introduced in TBX 2.7.

The URI handling logic is now able to switch from a different provider screen
back to Coder's main screen.

A short 2–3 second delay occurs while initializing the REST client, resolving the CLI, and generating the SSH config—during this time, there was no visual feedback indicating activity.