Avalonia for VSCode not working for remote development.

[l0hn]

Describe the bug

When woroking in VSCode using remote development the Avalonia extension does not work correctly. It gives the following error and output:

2024-09-05 10:55:20.961 [info] Creating language service
2024-09-05 10:55:20.961 [info] Starting Avalonia Language Server...
2024-09-05 10:55:20.961 [info] [Error - 10:55:20] Avalonia LSP client: couldn't create connection to server.
2024-09-05 10:55:20.961 [info] Launching server using command /usr/local/share/dotnet/dotnet failed. Error: spawn /usr/local/share/dotnet/dotnet ENOENT
2024-09-05 10:55:20.961 [info] Failed to start Avalonia Language Server. Launching server using command /usr/local/share/dotnet/dotnet failed. Error: spawn /usr/local/share/dotnet/dotnet ENOENT

### To Reproduce

- Use VSCode remote development over SSH and install the Avolnia extension in the remote host (in my case the local machine is macOS, and the remote machine is Windows)
- Open any axaml file for an avalonia project
- Observe error for LSP client unable to connect to server.

### Avalonia for VS Code

0.29, 0.30, 0.31

### Avalonia version

11.0.11

### VS Code version

1.92.2

### Relevant log output

```shell
2024-09-05 10:55:20.961 [info] Creating language service
2024-09-05 10:55:20.961 [info] Starting Avalonia Language Server...
2024-09-05 10:55:20.961 [info] [Error - 10:55:20] Avalonia LSP client: couldn't create connection to server.
2024-09-05 10:55:20.961 [info] Launching server using command /usr/local/share/dotnet/dotnet failed. Error: spawn /usr/local/share/dotnet/dotnet ENOENT
2024-09-05 10:55:20.961 [info] Failed to start Avalonia Language Server. Launching server using command /usr/local/share/dotnet/dotnet failed. Error: spawn /usr/local/share/dotnet/dotnet ENOENT

Additional context

No response