windows和wsl中都下载了iflow但二者无法同时使用的问题 English: Authentication Issues with iflow CLI in WSL When Windows Host is Already Authenticated

[Twinbox-dev]

当windows安装了iflow cli并认证登录之后(windows上可以正常使用iflow了)。
而如果在此windows上使用wsl(另外下载了iflow cli) 并想要认证使用便会出现问题：
1.浏览器访问认证的话，会长时间无法登录直至链接断开(此时windows端认证不受影响)
2.tokens认证的话，windows和wsl都会报api错误而导致双端都无法使用iflow cli

我不知道这是我的问题还是一个bug，故提出issue期望得到答复。

English：
After installing and successfully authenticating the iflow CLI on Windows (where it works normally), I encounter authentication problems when trying to use iflow within Windows Subsystem for Linux (WSL) on the same machine:

1. Browser-based authentication: When attempting to authenticate via the browser in WSL, the login process hangs indefinitely and eventually times out or disconnects. Notably, this does not affect the already authenticated Windows instance.
2. Token-based authentication: If I try to authenticate using tokens in WSL, both the WSL and Windows instances start reporting "API error" messages, rendering the CLI unusable on both sides.
   I'm unsure whether this is an environment-specific configuration issue on my end or an actual bug related to how iflow handles authentication across Windows and WSL environments. I’d appreciate guidance or confirmation on whether this is expected behavior or something that should be addressed.
   Thank you!