Fix Chrome CDP interface connection

[bgastelo]

These changes should fix the issue with connecting to the chrome runner.

This is the error message:

<js:/home/runner/work/opal/opal/lib/opal/cli_runners/node_modules/chrome-remote-interface/lib/chrome.js>:48:23:in `defaultTarget': No inspectable targets (Exception)
	from <js:/home/runner/work/opal/opal/lib/opal/cli_runners/node_modules/chrome-remote-interface/lib/chrome.js>:193:28:in `_fetchDebuggerURL'
	from node:internal/process/task_queues:95:5:in `processTicksAndRejections'
	from <js:/home/runner/work/opal/opal/lib/opal/cli_runners/node_modules/chrome-remote-interface/lib/chrome.js>:140:25:in `_start'

I based my changes on this comment from the repo: cyrus-and/chrome-remote-interface#445 (comment)

Testing locally, this seems to fix the main issue with CDP. However I am still seeing 2 errors in mspec:

1)
DateTime#to_date maintains the same julian day regardless of local time or zone FAILED
Expected 2456286 == 2456285
to be truthy but was false

2)
Time#wday returns an integer representing the day of the week, 0..6, with Sunday being 0 FAILED
Expected 3 == 4
to be truthy but was false

Maybe it's an issue with my local config?

Thanks,

Brandon

[hmdne]

This issue has been recently a problem on our CI, I have confirmed it locally too. Thank you for your hard work on debugging this issue!

Regarding the MSpec errors, those are related to the timezone and we have had many failures like that in the past :(