Merge 2a999178c273455a47688f74b48dcdebbab92c5a into a2cda21431765a24755f1eaf75135773fe245355

We believe these changes will fix the lint failure. The @types/chrome bump to ^0.3.0 reworked chrome.devtools.inspectedWindow.eval's overloads, and because EvalOptions has only optional properties, our existing two-argument callback call was structurally matching the Promise-returning overload instead of the callback overload, so ESLint flagged an unhandled floating promise. Passing undefined explicitly for the options argument forces TypeScript to resolve the callback overload, and widening updateSelectedComponentInfo's signature to accept the new exceptionInfo parameter keeps the callback type-compatible with that overload's stricter tuple signature.