Prove airgap bundle processing in AP inttest

[twz123]

Description

The Autopilot airgap inttest is operating on an already bootstrapped cluster. This means that all the images have already been pulled on the worker as soon as the Autopilot update kicks in. Hence, the update will succeed even if the airgap bundle functionality is broken.

To have an actual proof of correct processing, the inttest now checks the pinning of the images. Before the update, none of them should be pinned, after the update all of them.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update

How Has This Been Tested?

• Manual test
• Auto test added

Checklist:

• My code follows the style guidelines of this project
• My commit messages are signed-off
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I have checked my code and corrected any misspellings