Non ASCII paths causes ENOENT

**Enviroment:**
- OS: Windows 10 Home Single Language 64
- node: 14.15.4
- electron: 11.2.0
- electron-rebuild: 2.3.4

**Action taken:**
```npm install```

**Output:**
```
An unhandled error occurred inside electron-rebuild
spawn C:\Program Files (x86)\Programaci�n\VS2019CE\MSBuild\Current\Bin\MSBuild.exe ENOENT

Error: spawn C:\Program Files (x86)\Programaci�n\VS2019CE\MSBuild\Current\Bin\MSBuild.exe ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:269:19)
at onErrorNT (internal/child_process.js:465:16)
at processTicksAndRejections (internal/process/task_queues.js:80:21)
```

**_Note:_** The right path is `C:\Program Files (x86)\Programación\VS2019CE\MSBuild\Current\Bin\MSBuild.exe`.

**Workaround:**
- Reinstall in another folder with all ASCII characters (it was no fun).

Start by reproducing the reported `npm install` failure on Windows with a non-ASCII Visual Studio installation path. Trace how electron-rebuild locates and launches MSBuild, comparing the corrupted path in the error with the correct path shown in the report. Done means native module rebuilding works with non-ASCII paths and the behavior is covered by an appropriate test.

Written by the indexing model from the issue text.