emrun --system_info throws "No module named 'win32com'" on windows

This is a low priority bug of a forgotten dependency resulting in some errors when using emrun, but otherwise not impacting its usage.
Version of emscripten/emsdk:

```console
emcc (Emscripten gcc/clang-like replacement + linker emulating GNU ld) 3.1.38 (9eff02bc816c50ab0e3b70a3bd5b72a8dc2893a2)
clang version 17.0.0 (https://github.com/llvm/llvm-project 004bf170c6cbaa049601bcf92f86a9459aec2dc2)
Target: wasm32-unknown-emscripten
Thread model: posix
InstalledDir: C:\\min\home\artsimow\build\emsdk\upstream\bin
```

Running `emrun --system_info index.html` throws the following error on Windows 10 22H2:

```
Time of run: 06/22/23 13:57:28
Traceback (most recent call last):
File "C:\\min\home\artsimow\build\emsdk\upstream\emscripten\emrun.py", line 782, in get_cpu_info
from win32com.client import GetObject
ModuleNotFoundError: No module named 'win32com'

Computer name:
Model: ,
OS: Windows 10 Enterprise (64bit) with -1 MB of System RAM
CPU: Unknown ("No module named 'win32com'"), 0 MHz, 1 physical cores, 1 logical cores
GPU0: Intel(R) UHD Graphics, driver version 31.0.101.1999 (5-31-2022) with 1024 MBs of VRAM
GPU1: NVIDIA Quadro T2000 with Max-Q Design, driver version 31.0.15.1801 (2-15-2023) with 4095 MBs of VRAM
UUID: 70f41894-e732-4da0-8ccc-40f64d566c32
Now listening at http://0.0.0.0:6931/
```
Except no information being given about the CPU, the script runs fine.
Doing a manual install of `pywin32` doesn't solve it, so it's a bit more involved.