Fixing version comparison & adding support for build comparisons

[pudquick]

This is both a bug fix and a new feature.

First the bug fix - here's an example situation:

• expectedVersion set to: 10.14.3
• systemVersion read as: 10.15.1

This logic: https://github.com/google/macops/blob/master/deprecation_notifier/DeprecationNotifier/DNAppDelegate.m#L60-L63

  } else if (([expectedVersionArray[0] intValue] <= [systemVersionArray[0] intValue]) &&
             ([expectedVersionArray[1] intValue] <= [systemVersionArray[1] intValue]) &&
             ([expectedVersionArray[2] intValue] <= [systemVersionArray[2] intValue])) {
    NSLog(@"Exiting: OS is already %@ or greater", expectedVersion);

10 <= 10: true 14 <= 15: true 3 <= 1: false

The comparison will fail when it shouldn't.

This PR includes better comparison logic.

It additionally adds support for a new optional Localizable string value: expectedBuilds

The value of this string should be a comma delimited string (no spaces) of allowed builds.

If the OS is detected to be exactly the expectedVersion, then:

• if no expectedBuilds is defined, Deprecation Notifier will determine the OS meets the requirement
• if expectedBuilds is defined, the system build is looked for in expectedBuilds - if and only if the build is present, then the OS meets the requirement

Use case: for environments that are supporting a major OS version which has now gone into Security Updates, Deprecation Notifier is unable to tell a "fully patched" OS version without looking at the build information.

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

:memo: Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

[pudquick]

I signed it!

[googlebot]

CLAs look good, thanks!