Failed to run .net application with related path

Describe the bug

When running .net executable from nushell, it won't start if the command line is related file path, such as:
.\ILSpy_binaries_7.2.1.6856\ILSpy.exe

From fuslogvw, I can see something wrong in the log:

*** Assembly Binder Log Entry  (2023/7/12 @ 13:30:27) ***

The operation was successful.
Bind result: hr = 0x0. The operation completed successfully.

Assembly manager loaded from:  C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Running under executable  \\?\F:\Software\ILSpy_binaries_7.2.1.6856\ILSpy.exe
--- A detailed error log follows. 

=== Pre-bind state information ===
LOG: DisplayName = WindowsBase, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
 (Fully-specified)
LOG: Appbase = file://?/F:/Software/ILSpy_binaries_7.2.1.6856/
LOG: Initial PrivatePath = NULL
LOG: Dynamic Base = NULL
LOG: Cache Base = NULL
LOG: AppName = ILSpy.exe
Calling assembly : (Unknown).
===
LOG: This bind starts in default load context.
LOG: No application configuration file found.
LOG: Using host configuration file: 
LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\config\machine.config.
LOG: Found assembly by looking in the GAC.
LOG: Binding succeeds. Returns assembly from C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\WindowsBase\v4.0_4.0.0.0__31bf3856ad364e35\WindowsBase.dll.
LOG: Assembly is loaded in default load context.

Firstly the command line now starts with " \?".
Secondly, it reports "LOG: No application configuration file found.", which the ILSpy.exe.config exists and placed in the same directory of ILSpy.exe.

I try other .net application, it has the same problem.

But if I use the absolute file path, it runs fine!

And the previous strange log are gone (No more starts with "\?" and report "No application configuration file found."

How to reproduce

Prepare any .net executable, such as ILSpy.exe (download from https://github.com/icsharpcode/ILSpy/releases)
run the executable with related path, such as .\ILSpy.exe

Expected behavior

The application runs fine.

Screenshots

No response

Configuration

Additional context

No response

Reproduce the issue on Windows with a .NET executable invoked as .\ILSpy.exe, then compare it with the equivalent absolute path. Trace Nushell's command-path handling and verify that relative invocation preserves the executable directory and configuration lookup so the application starts normally.