Correctly handle version downgrades (e.g. via TestFlight)

[cpraehaus]

Description of Change

Version downgrades (e.g. from "1.1.0" to "1.0.1") are possible on certain platforms (e.g. on iOS with TestFlight) and thus should be handled correctly by VersionTracking module - especially if the version was already installed previously.

Since this is a bugfix (not a feature) covered by unit tests no samples are provided (see PR checklist).

Bugs Fixed

• Related to issue [Bug] VersionTracking does not handle downgrades correctly #1960

API Changes

None

Behavioral Changes

Observable behavior/semantics of the following API elements can change but only in downgrade scenarios described above:

• VersionTracking.IsFirstLaunchForCurrentVersion
• VersionTracking.IsFirstLaunchForCurrentBuild
• VersionTracking.PreviousVersion
• VersionTracking.PreviousBuild
• VersionTracking.FirstInstalledVersion
• VersionTracking.FirstInstalledBuild
• VersionTracking.VersionHistory
• VersionTracking.BuildHistory
• VersionTracking.IsFirstLaunchForVersion()
• VersionTracking.IsFirstLaunchForBuild()

PR Checklist

• Has tests (if omitted, state reason in description)
• Has samples (if omitted, state reason in description)
• Rebased on top of main at time of PR
• Changes adhere to coding standard
• Updated documentation (see walkthrough)

[ghost]

All CLA requirements met.

[jamesmontemagno]

@mattleibow since you wrote this if you can take a look at it.

[jfversluis]

Edit: nope, I am totally mistaken with what I wrote earlier. This seems good to me :)