Enhancements possible for packer-image pipeline

[smerle33]

Summary

When creating Pull Request on packer-images repository the pipeline check all matrix elements, it takes time, and money plus it often fail for timeout.

Those tests can be limited for Pull Request and run the full batch for main and tags.

[x] - We can also prevent the publication of those images on both amazon (https://developer.hashicorp.com/packer/integrations/hashicorp/amazon/latest/components/builder/ebs) and azure (https://developer.hashicorp.com/packer/integrations/hashicorp/azure/latest/components/builder/arm)

Now the matrix contains:

CPU ARCHITECTURE : amd-intel / arm64
OS: window / linux
OS VERSION: windows 2022 / windows 2019 / Ubuntu 22.04
PROVIDERS: Docker / Amazon / Azure

We can limit by architecture

• docker linux amd-intel ubuntu 22.04 (around 20mn)
• docker linux arm64 ubuntu 22.04 (around 20mn)
• AWS linux amd-intel ubuntu 22.04 (around 30mn)
• ** AWS windows 2019 ** (here a great option would be to not test on windows except if a label / or / commit message explicitly asked for it ... not sure it's possible / check on file change if build on windows are needed)
  • option of a "fullscan" label to force full checks
  • by default, check on linux only expect if files concerning windows are changed (checkout scm + when file change)

and once the windows will be available as kubernetes pods, we would be able to add them in PR checks

We could also analyse the file list impacted within the PullRequest to limit the tests, for example if the windows provider file [windows-provision.ps1](https://github.com/jenkins-infra/packer-images/blob/main/provisioning/windows-provision.ps1)is modified, we have to play a windows test.