impl: add the option to disable ssh wildcard configuration (#584)

* impl: add the option to disable ssh wildcard configuration

It will be used later by the Coder Settings view to allow users
to enable or disable SSH hostname wildcard configuration.

* impl: expose ssh wildcard config in the Settings page

Updated the UI component to allow configuration by the user

* impl: take into account wildcard configuration

when generating the ssh config for Coder Gateway.
Up until now we just checked if the Coder deployment supports
this feature, but now users have to option to continue to
use expanded hostnames in the ssh config.

* fix: force CLI manager to use user settings

CLIManager can be created with default settings (simplifies testing),
among which the ssh wildcard config is enabled. But in reality the
config can be disabled by the user.

* impl: ability to start a recent workspace connection after ssh wildcard config was changed

Currently, if a user starts a connection with wildcard enabled and then later on it disables
the 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 to
open 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 workspace

Connections 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.

fix: relaxed SNI hostname resolution (#579)

* fix: relaxed SNI hostname resolution

When establishing TLS connections, SNI resolution may fail if the configured altHostname contains `_` or
any 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 issue
only 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

chore: bump actions/checkout from 4.2.2 to 5.0.0 (#571)

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>

impl: add support for disabling CLI signature verification (#564)

* impl: add new configurable option to disable CLI signature verification

These options are configurable from the Settings page there is no available
shortcut on the main plugin page to discourage the quick disable of CLI verification

* impl: hide configurable fallback if signature verification is disabled

The main plugin screen has a quick shortcut for setting whether the user
wants to fallback on releases.coder.com for signatures if they are not provided by
the main deployment. This checkbox should not be visible if the user wants to disable
signature verification altogether.

* impl: skip signature validation

Signature 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

impl: verify cli signature (#562)

* impl: support for downloading and verifying cli signatures

* fix: class cast exception

* impl: embed the pgp public key as a plugin resource

This is the key that validates if the gpg signature was tampered

* chore: fix UTs related to CLI downloading

For one thing some method signature changed, some methods are now suspending functions
that will have to run in a coroutine in the tests. The second big issue is that now
the download function requests user's input via a dialog

* fix: download the correct CLI signature for Windows

The signature for windows CLI follows the format: coder-windows-amd64.exe.asc
Currently it is coded to coder-windows-amd64.asc which means the plugin
always fail to find any signature for windows cli

* chore: next version is 2.22.0

* impl: strict URL validation for the connection screen

This commit rejects any URL that is opaque, not hierarchical, not using http or https
protocol, or it misses the hostname.

* impl: strict URL validation for the URI handling

This commit rejects any URL that is opaque, not hierarchical, not using http or https
protocol, or it misses the hostname.

* fix: transform to url only after we checked the validation result

* chore: update UT expected result

fix: marketplace logos should use the new design (#557)

* fix: marketplace logos should use the new design

# Conflicts:
#	CHANGELOG.md

* chore: next version should be 2.21.1

impl: update icons to match the new branding (#555)

* impl: update icons to match the new branding

* fix: eap build is no longer available for verification

In the previous PR 2025.2 EAP build was available on the default repositories,
it no longer seems the case. Additionally, I've configured the verification
phase to use the latest available 2024.3 patch (6 patches available)

* chore: next version is 2.21.0

fix: pass the folder parameter to the IDE&Project dialog (#550)

* chore: use newer snapshot build for testing and building

I've also changed the list of Gateway versions we run the verifier against
to include Gateway 2025.1 while excluding some ancient releases.

Without this commit the PR will fail to build, the declared snapshots are
no longer available in the repository

* fix: pass the folder parameter to the IDE&Project dialog

The value of the `folder` URI parameter is passed to the IDE&Project
dialog when handling URIs. The folder value will be rendered instead
of the default home folder if the value is not blank.

-resolves #466

* chore: next version is 2.20.1

update version