tests(smoke): support full chrome version for pruning

[connorjclark]

Two commits here:

1. Add full version string support for the _minChromium/_maxChromium properties. Just the milestone number is too coarse to be useful for addressing regressions that have immediately occurred in ToT (but not landed in canary).
2. temporarily ignore smoke failure for deprecations audit, so unblock CI. see InspectorIssues protocol no longer contains message strings for deprecations #13895

[connorjclark]

This is what ToT CDT does right now (but not for much longer, there's a pending CL): just hides these translated strings.

[brendankenny]

ideally if we're going to be exporting a function and testing it, it would be the whole kit and caboodle, like expect(failsChromeVersionCheck(hostVersion, {_minChromiumVersion: '100'}).toBe(whatever)

[connorjclark]

done

[brendankenny]

Oh, I meant more like

/**
 * @param {string} hostVersionString
 * @param {*} obj
 */
function failsChromeVersionCheck(hostVersionString, obj) {
  const hostVersion = hostVersionString.split('.').map(Number); // or keep parseVersion()
  if (obj._minChromiumVersion) {
    const minVersion = obj._minChromiumVersion.split('.').map(Number);
    for (let i = 0; i < hostVersion.length; i++) {
      if (hostVersion[i] < minVersion[i]) return true;
    }
  }
  if (obj._maxChromiumVersion) {
    const maxVersion = obj._maxChromiumVersion.split('.').map(Number);
    for (let i = 0; i < hostVersion.length; i++) {
      if (hostVersion[i] > maxVersion[i]) return true;
    }
  }

  return false;
}

so it's not in several pieces and it avoids having to remember the -1/1 convention.

Up to you, but let's land whatever so we can unblock CI

[connorjclark]

Framing it as a comparator function helps me understand (or at least write?) these things better, so I'll keep it like this. splitting it out is a good for readability, thanks for recommending.