HW test optimizations

[Kampi]

• Pass J-Link serial and hardware revision as arguments to pytest
• Add a setup for different hardware revisions and J-Links to CI/CD
• Add support for ARM 64
• Add support for PPK2
• Skip the test when the target J-Link isn´t connected
• Device recovering
• Test report

[ldab]

So the way I imagined it is like

1. yml file has a matrix with Self-runner name + HW version + Serial
2. Pytest …. $matrix

The self hosted runner name is important on a matrix because I have one now, Jakob may set up another one and so on…. And maybe we need another argument with features if you set up one with a PowerProfiler 🤯 so that not all tests would apply anymore

So the way I imagined it is like

1. yml file has a matrix with Self-runner name + HW version + Serial
2. Pytest …. $matrix

The self hosted runner name is important on a matrix because I have one now, Jakob may set up another one and so on…. And maybe we need another argument with features if you set up one with a PowerProfiler 🤯 so that not all tests would apply anymore

I added two matrices for the J-Links and the HW revisions so we can start in a simple way with it. Ofc we need a way to pass options because maybe you also want to compare debug and release build too.

Seem right, @jakkra I thought computer name can be passed as argument but apparently only labels https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/using-self-hosted-runners-in-a-workflow#about-self-hosted-runner-labels can you please check what labels are available on this runner?