`explorer.exe` should be added to the list of executables to apply legacy argument passing to when `$PSNativeCommandArgumentPassing` is set to `Windows`

Summary of the new feature / enhancement

When explorer.exe is passed a double-quoted path whose value ends in \, it (mistakenly) expects the closing \" sequence not to be escaped as \\" (the latter escaping now (sensibly) happens by default, whereas the unescaped form is what Windows PowerShell (mistakenly) passes).

That is, for instance, explorer.exe 'C:\Program Files\' currently quietly fails (notably, this form, with a trailing \, is created by tab-completion) with Windows as the $PSNativeCommandArgumentPassing mode (which is the default on Windows): the path isn't recognized and File Explorer defaults to the Documents folder.
For background information, see https://github.com/PowerShell/PowerShell/issues/26422#issuecomment-3517902966

Proposed technical implementation details (optional)

Add explorer to the list of processes at https://github.com/PowerShell/PowerShell/blob/4aa65a77be93911072e015f2a52656786c8f54bf/src/System.Management.Automation/engine/NativeCommandProcessor.cs#L215 so as to make it exhibit the same (broken) behavior as Windows PowerShell by default, to match explorer.exe's own broken behavior.

Note: A prerequisite for this implementation to take effect is fixing the following issue:

• #26432

Read src/System.Management.Automation/engine/NativeCommandProcessor.cs around line 215 and review prerequisite issue #26432 first. Confirm how the executable list is used for Windows argument passing, then verify that explorer.exe is covered by the requested legacy handling once the prerequisite is resolved.