Share an alternative management method for protocols such as RDP/VNC/HTTPS

Although WindTerm does not integrate RDP/VNC and other connection protocols, it can implement a workaround for access management through **Shell** sessions.

Take RDP as an example:
- Create a new Shell session
- Session page: Set **Label**, select Windows icons
- Shell-process page: set **Execute Command after start**, you can choose mstsc.exe under Windows, freeRDP under Linux, etc
```bash
# Only the ip parameter is applied here, which can be extended as needed
# The last \r is a carriage return, otherwise you need to manually hit enter to execute the command
# You can also use a RDP file to implement passwordless login

mstsc.exe /v: \r

```

The end result is that the windterm manages all connections as an address book
- For self-supported connections such as ssh/telnet/serial, open in the windterm window
- For unsupported connections such as RDP/VNC, etc, you can open them in a separate window through the command，like RemoteDesktopManager.

Some commands are written as follows
- https: `Start-Process -FilePath \r`
- vsphere client: ` & 'C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\VpxClient.exe' -s -u -p \r`
- Sunlogin: `& 'C:\Program Files\Oray\SunLogin\SunloginClient\SunloginClient.exe' --mod=fastcontrol --fastcode= --pwd= \r`


No repository file, test, or entry point is named. Start by reviewing the existing Shell session workflow, including the Session page and Shell-process setting for executing a command after startup; done would require a clear, maintained description of the workaround for launching external RDP, VNC, HTTPS, or similar clients.

Written by the indexing model from the issue text.