CI check for new deprecation strings from devtools

#13961 starts to pull strings for the deprecation audit from devtools

We need a way to keep this updated. Options:

1) Do something like `third-party/chromium-synchronization/inspector-issueAdded-types-test.js`
1) Regularly update (with a bot?) the `chrome-devtools-frontend` package

I'd like to evaluate the second option first, we shouldn't keep adding one-off checks as we continue pulling different things from devtools.

Start by reviewing #13961 and the existing third-party/chromium-synchronization/inspector-issueAdded-types-test.js check. Investigate the chrome-devtools-frontend package update option first, then compare it with the existing one-off check approach. Done means CI stays updated as devtools deprecation strings change without adding another one-off check.

Written by the indexing model from the issue text.