- will also reflect on the jar/zip name

- copied from coder gateway plugin

- the API for browsing url(s) is no longer available- this patch implements a basic URL opener that  relies on native tools.

- if successfully signed in we go back to the  main page which shows the environments/workspaces- similar approach if user hits Cancel during sign in- `EnvironmentUiPageManager` is an undocumented Toolbox  component that has more flexibility to navigate between pages

- the connection status was unreadable due to the background  and foreground colors used. The latest Toolbox version  comes with standard color palettes that change based  on the theme and environment state.- plus some small extra refactorings that reduce the number  of constructor parameters and rely on the service locator

- url was not displayed in the env page until the rest  client was connected- but we don't need to wait for the rest client to connect,  the url is already available from settings

- Toolbox does not provide a plugin manager interface with metadata about current plugin.  So we had to implement one for ourselves in order to have simple things like plugin version.- the implementation relies on the extension.json which is deployed in the root of the  jar (i.e. the plugin jar)- the rest of the json fields are ignored for now

- use plugin's version

- Toolbox 2.6.0.38311 comes with new plugin API dependencies

- Toolbox 2.6.0.38311 runs with Kotlin stdlib 2.1.0  therefore I've upgraded the Kotlin compiler to match the runtime.- similarly coroutines, serialization and KSP support had to be upgraded.

- due to new API for remote environment model

- due to new API for SSH environment view

- a couple of functions on the existing models and views  transformed into class properties- while other functions are now suspend functions

- the plugin was loading so no classloading issues related to logging classes, but it was not logging  anything from the plugin.- the tinylog dependency was apparently ignored. Until we receive a definitive answer from JetBrains  we have two options: either propagate the service locator and the logging service to every component  (even non UI models/views) or wrap the toolbox logging service in a slf4j implementation with minimal  invasive changes.- the latter approach is possible because no component is initialized until CoderToolboxExtension is called.  That means we have the chance to initialize our custom logger factory around the toolbox logger service.