Merge c81c28c04c04ba124b5395c207ce22df63ed1ca7 into a2cda21431765a24755f1eaf75135773fe245355

We updated the callback passed to chrome.devtools.inspectedWindow.eval so it matches the @types/chrome 0.3 callback signature, which also passes the exception info as a second argument. Our old one-argument callback matched no overload, so TypeScript fell back to the Promise overload and no-floating-promises flagged the call. With the matching signature the callback overload is selected and the lint error goes away.