ml command name conflict with MSVC x86 toolchain ml.exe #589

Describe the bug

Same as title description.

This bug happens on Windows platform, with using Visual Studio Developer Command Prompt targeting x86 platforms, ml.cmd name will conflict to Microsoft Macro Assembler ml.exe.

To Reproduce

Serveral conditions together will override/conflict:

• Modules/bin in PATH or PowerShell initialized by Modules/init/pwsh.ps1.
• Visual Studio Developer Command Prompt is targeting x86 platforms.

Modules version and configuration

Tested on 5.6.0 version. But It could happens on any version if there's ml.cmd.

Additional context

I was writing some system msvc env detection script with Modules installed on my device, and this happens.

Below is a PrtSc of test result.

This PowerShell is a VS2015 x86 native environment, have Modules/bin not in PATH but initialized by Modules/init/pwsh.ps1.

As we can see, ml.cmd is not in PATH but overrides ml.exe.