Windows MSI installer doesn't add `adguarddns-cli` to `PATH`

### Prerequisites

- [x] I have checked the [Knowledge Base](https://adguard-dns.io/kb/) and the [Discussions](https://github.com/AdguardTeam/AdGuardDNSCLI/discussions) and found no answer

- [x] I have searched other issues and found no duplicates

- [x] I want to report a bug and not [ask a question or ask for help](https://github.com/AdguardTeam/AdGuardDNSCLI/discussions/categories/q-a)

- [x] I have set up AdGuard DNS CLI correctly and configured clients to use it. (Use the [Discussions](https://github.com/AdguardTeam/AdGuardDNSCLI/discussions/categories/q-a) for help with installing and configuring clients.)

### Platform (OS and CPU architecture)

Windows, AMD64 (aka x86_64)

### Installation

GitHub releases

### Setup

On a personal machine

### AdGuard DNS CLI version

0.1.1

### Action

1. Install AdGuard DNS CLI on Windows using the MSI installer from the release page.
2. Open a new PowerShell or Command Prompt window.
3. Run:
```sh
adguarddns-cli --version
```

or:
```powershell
Get-Command adguarddns-cli
```
4. Observe that the command is not found.

### Expected result

After installing AdGuard DNS CLI using the Windows MSI installer, the `adguarddns-cli` command should be available from a regular terminal session, for example PowerShell or Command Prompt.

This would make it possible to run commands from the documentation, such as:

```sh
adguarddns-cli --version
adguarddns-cli -s status -v
adguarddns-cli -s start -v
```

### Actual result

After installing AdGuard DNS CLI using the Windows MSI installer, the installation directory is not added to the system or user `PATH`.

As a result, Windows cannot find the executable:
```powershell
Get-Command adguarddns-cli
```

returns nothing, and running:
```sh
adguarddns-cli --version
```
fails because the command is not recognized.

### Additional information and/or screenshots

The [documentation](https://adguard-dns.io/kb/dns-client/overview/) says that on Windows users should download and install using the MSI installer. However, after installation the CLI executable is not available in `PATH`, so it is not possible to configure or manage AdGuard DNS CLI from a normal terminal without manually locating the installation directory or manually editing `PATH`.

It would be helpful if the MSI installer added the installation directory to `PATH`, or if the Windows documentation explicitly explained where the executable is installed and how users are expected to run it.