Fixes #77 - Kill chrome process on Windows after quitting the driver
On a Windows VM I observed that running the chromium beta (v124) tests produced many chrome processes that would never get closed:
> Get-Process chrome
Handles NPM(K) PM(K) WS(K) CPU(s) Id SI ProcessName
------- ------ ----- ----- ------ -- -- -----------
121 13 6380 15092 0.06 1720 1 chrome
381 36 69144 109416 194.00 2000 1 chrome
121 13 6376 15112 0.28 2324 1 chrome
280 28 27576 42548 0.77 3732 1 chrome
137 14 6944 15732 0.17 4500 1 chrome
200 16 7548 17724 0.19 5144 1 chrome
426 37 42040 66080 2.63 5412 1 chrome
285 33 31156 51020 4.27 6336 1 chrome
137 14 6956 15744 0.14 7112 1 chrome
0 73 74988 213584 22.22 7236 1 chrome
169 15 7688 18324 0.44 8136 1 chrome
376 35 65452 105764 101.23 8352 1 chrome
373 35 54640 85756 179.61 8712 1 chrome
378 36 71040 111312 127.28 8880 1 chrome
137 14 7280 16456 0.17 10052 1 chrome
423 46 41252 72572 9.00 10312 1 chrome
Killing those chrome processes on Windows after quitting the driver fixes the issue.