Integration tests

[vijaiaeroastro]

This PR includes the integration tests to the existing build.yml script. This completes the issue #361.

It has 3 actions:

integration-tests-latest-commit
integration-tests-latest-release
integration-tests-last-two-releases

All of the integration tests dynamically choose the latest test performance suite from 3MFConsortium/test_suites. It picks the latest test suite zip file from the releases section automatically.

• In the first action, it picks the SDK artifact from the current commit and runs the integration test using that SDK.
• In the second case, the action automatically determines the latest release from the lib3mf repository, downloads the SDK, and runs the integration tests on that SDK.
• In the third scenario, the action determines the latest release dynamically along with the release before that, runs the integration tests on both of them, and makes a simple comparison against the total script execution time.

The latest commit action is triggered on every build. The other two have an if condition that checks if the current action is being run on a release event and only allows it in that scenario. The trigger condition can be commented/uncommented based on further discussions.

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 71.10%. Comparing base (6c92731) to head (658de28). Report is 3 commits behind head on develop.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## develop #367 +/- ## ======================================== Coverage 71.10% 71.10% ======================================== Files 271 271 Lines 30307 30307 ======================================== Hits 21551 21551 Misses 8756 8756 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[vijaiaeroastro]

@gangatp All of your requests have been incorporated. There is now an additional job that checks the last commit against the last release and an artifact is also produced with the comparison info as shown below.

A new environment variable is introduced in the build.yml file itself to turn integration tests on / off

The pipeline looks like this now

The last block of jobs with integration tests would not be run if its turned off. We can also have 4 separate variable for 4 different integration tests and have more fine grained control over turning them on / off.

Let me know if anymore changes are required in this.

[vijaiaeroastro]

@gangatp All of Cmake stuff is also now merged into this without conflicts. It can be merged into develop without issues :)

[vijaiaeroastro]

• LIB3MF_VERSION variable is now inferred from the CMakeLists.txt
• CPack examples are not packed along with the SDK anymore but they are still tested in the deploy stage
• Python bindings have a test in all 3 platforms
• All the action recipes used were upgraded to the latest ones to reduce warnings in github actions. Code coverage action is kept back since the newer version reports drastically lower coverage and causes failure

[vijaiaeroastro]

Thanks a lot for taking the time Pradeep. I have merged. Did you have conflicts with your branch ? The automated check from Github did not report any conflicts. I will check once more in develop branch.