* Changelog update - v2.22.0* chore: empty commit to trigger CI---------Co-authored-by: GitHub Action <action@github.com>Co-authored-by: Faur Ioan-Aurel <fioan89@gmail.com>

* impl: add new configurable option to disable CLI signature verificationThese options are configurable from the Settings page there is no availableshortcut on the main plugin page to discourage the quick disable of CLI verification* impl: hide configurable fallback if signature verification is disabledThe main plugin screen has a quick shortcut for setting whether the userwants to fallback on releases.coder.com for signatures if they are not provided bythe main deployment. This checkbox should not be visible if the user wants to disablesignature verification altogether.* impl: skip signature validationSignature validation is skipped if the user configured the `disableSignatureVerification` to true.* chore: update changelog* chore: next version is 2.22.1* doc: developer facing documentation for CLI signature verification* chore: fix UTs

* Changelog update - v2.22.1* chore: trigger CI---------Co-authored-by: GitHub Action <action@github.com>Co-authored-by: Faur Ioan-Aurel <fioan89@gmail.com>

* fix: don't create new api keys each time we do workspace pollingThe default behavior for `coder login --token <token>` is to:- use the provided token temporarily to authenticate the login process- generate a new session token and stores that for future CLI use- the original token provided is not stored or reusedThe Coder `Recent projects` view polls every 5 seconds for workspaces frommultiple Coder deployment. The polling process also involves a callto the `cli.login`. The cli is later used start workspaces if user clicks ona project for which the workspace is stopped. Instead of generating a new tokeneach time we login we can use the `coder login --use-token-as-session --token <token>` which:- uses the provided token directly as the session token- stores the original token for future CLI commands- no new token is generated* refactor: only login the cli when starting workspacesThe Coder `Recent projects` view polls every 5 seconds for workspaces frommultiple Coder deployment. The polling process also involves a callto the `cli.login`. The cli is later used to start workspaces if a user clicks ona project for which the workspace is stopped. The login can be called on demand, onlywhen a "recent" project is stopped and the user wants to start it. This commitreduces a lot of overhead associated with spawning cli commands every 5 seconds.* chore: next version is 2.22.2

Bumps [actions/setup-java](https://github.com/actions/setup-java) from 4 to 5.- [Release notes](https://github.com/actions/setup-java/releases)- [Commits](actions/setup-java@v4...v5)---updated-dependencies:- dependency-name: actions/setup-java  dependency-version: '5'  dependency-type: direct:production  update-type: version-update:semver-major...Signed-off-by: dependabot[bot] <support@github.com>Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>Co-authored-by: Faur Ioan-Aurel <fioan89@gmail.com>

Bumps [actions/checkout](https://github.com/actions/checkout) from 4.2.2 to 5.0.0.- [Release notes](https://github.com/actions/checkout/releases)- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)- [Commits](actions/checkout@v4.2.2...v5.0.0)---updated-dependencies:- dependency-name: actions/checkout  dependency-version: 5.0.0  dependency-type: direct:production  update-type: version-update:semver-major...Signed-off-by: dependabot[bot] <support@github.com>Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>Co-authored-by: Faur Ioan-Aurel <fioan89@gmail.com>

* Changelog update - v2.22.2* chore: trigger GH build---------Co-authored-by: GitHub Action <action@github.com>Co-authored-by: Faur Ioan-Aurel <fioan89@gmail.com>

* fix: relaxed SNI hostname resolutionWhen establishing TLS connections, SNI resolution may fail if the configured altHostname contains `_` orany other characters not allowed by domain name standards (i.e. letters, digits and hyphens).This change introduces a relaxed SNI resolution strategy which ignores the LDH rules completely.Because this change goes hand in hand with auth. via certificates, I was able to reproduce the issueonly via UTs. At this point the official Coder releases supports only auth. via API keys.-fixes#577* chore: next version 2.22.3* chore: remove leftover debug liness

* Changelog update - v2.22.3* chore: trigger CI build---------Co-authored-by: GitHub Action <action@github.com>Co-authored-by: Faur Ioan-Aurel <fioan89@gmail.com>

* Update README.mdadded note to recommend the Toolbox plugin* Update README.mdAdded link to docs

* impl: prefer agent name over agent id in URI handlerAgent name is easier to resolve in jetbrains gateway module* impl: prefer agent name over agent id in URI handler (2)Error reporting should also prefer agent name over the agent id.* chore: update and fix UTsTest cases related to agent matching have to be updatednow that agent name is preferred over agent id.* chore: refactor UTs related to agent matching in URI handlingRewrote the entire test to be easier to read and debug.

* impl: add the option to disable ssh wildcard configurationIt will be used later by the Coder Settings view to allow usersto enable or disable SSH hostname wildcard configuration.* impl: expose ssh wildcard config in the Settings pageUpdated the UI component to allow configuration by the user* impl: take into account wildcard configurationwhen generating the ssh config for Coder Gateway.Up until now we just checked if the Coder deployment supportsthis feature, but now users have to option to continue touse expanded hostnames in the ssh config.* fix: force CLI manager to use user settingsCLIManager can be created with default settings (simplifies testing),among which the ssh wildcard config is enabled. But in reality theconfig can be disabled by the user.* impl: ability to start a recent workspace connection after ssh wildcard config was changedCurrently, if a user starts a connection with wildcard enabled and then later on it disablesthe wildcard config then the recent connections becomes unusable because the hostnames are invalid.The issue can reproduce the other way around as well (start with wildcard ssh config disabled,start an IDE and then later on enable wildcard config)This commit addresses the issue by resolving the hostname on demand when the user wants toopen the remote IDE from the recent connections panel.* chore: update README* chore: next version is  2.23.0* fix: don't show twice the connection to the same workspaceConnections started with two different hostnames (because of the ssh wildcard config)can be rendered twice in the Recent projects panel.With this commit we ignore the hostname and instead use the workspace name and deployment URL.

* Changelog update - v2.23.0* chore: for build trigger---------Co-authored-by: GitHub Action <action@github.com>Co-authored-by: Faur Ioan-Aurel <fioan89@gmail.com>