feat: Add aircraft version check and user message when using old version

[frankkopp]

Summary of Changes

This PR introduces a check of the version of the currently running aircraft against the latest github versions.

This PR adds a comprehensive version tag to the a32nx_build_info.json which is then used in the EFB code to check against the github version. A MSFS notification will be shown and the flyPad will also show the old version state in the status bar.

Notification policy:

• when the version is older than the latest Stable release
• when version is equal or newer and branch is dev or exp then compare commit hash
  • if different and build date of aircraft is older than build date of latest dev/exp commit by 3 days

Screenshots (if necessary)

2022-12-26_13h48_02.mp4

Discord username (if different from GitHub): Cdr_Maverick#6475

Testing instructions

To test this the a32nx_build-info.json file needs to be edited to "pretend" to be on an outdated version.

All editions;

• To check for outdated main version change the version info to an older version (e.g. 0.9.0)

Dev and Exp

• Change the version tag to something like v0.10.0-dev.124567 or v0.10.0-exp.124567
• As long as the commit sha is different to the last commit in dev or exp it will check for build time.
  • If older than 3 days the message should appear - change the built date to test this
• If commit sha is identical no message should appear. (change the commit sha in the version string)

How to download the PR for QA

Every new commit to this PR will cause a new A32NX artifact to be created, built, and uploaded.

1. Make sure you are signed in to GitHub
2. Click on the Checks tab on the PR
3. On the left side, click on the bottom PR tab
4. Click on the A32NX download link at the bottom of the page

[mico975]

Quality Assurance Tester Report

Discord : mico#3145
Object of testing: #7655
Tier of Testing : 1
Date : 01/01/2023

Testing Process:
To check for outdated main version change the version info to an older version (e.g. 0.9.0) - OK

Change the version tag to something like v0.10.0-dev.124567 or v0.10.0-exp.124567
As long as the commit sha is different to the last commit in dev or exp it will check for build time.
If older than 3 days the message should appear - change the built date to test this - OK
If commit sha is identical no message should appear. (change the commit sha in the version string) - OK

Negatives:
N/A

Testing Results:
Passed

Conclusions:
LGTM

Media: