Introduce hw-test job

[ozan956]

Add a workflow_call entrypoint that checks out hw-test and runs a test set on the shared labgrid hardware pool via the run-test action.

PR Type

• Bug fix (a change that fixes an issue)
• New feature (a change that adds new functionality)
• Breaking change (a change that affects other repos or cause CIs to fail)

PR Checklist

• I have conducted a self-review of my own code changes
• I have compiled my changes, including the documentation
• I have tested the changes on the relevant hardware
• I have updated the documentation outside this repo accordingly
• I have provided links for the relevant upstream lore

[gastmaier]

devicetrees are all built into a single dtb by the https://github.com/analogdevicesinc/linux/blob/ci/.github/workflows/compile-devicetrees.yml workflow, generating like https://broadcasts.cloudsmith.com/adi/linux/t1qeCn7Sxp6h

this allow to build many, almost all, devicetrees much faster, which also compress nicely since they are mostly the same.

verify if the existing dtb artifact satisfy your needs

[ozan956]

devicetrees are all built into a single dtb by the https://github.com/analogdevicesinc/linux/blob/ci/.github/workflows/compile-devicetrees.yml workflow, generating like https://broadcasts.cloudsmith.com/adi/linux/t1qeCn7Sxp6h

this allow to build many, almost all, devicetrees much faster, which also compress nicely since they are mostly the same.

verify if the existing dtb artifact satisfy your needs

Will test it, but I was matching the artifact name with the board name, for example I was looking for sc598 and ezkit to match, I believe this job just puts everything in another artifact. I can also change the logic of hw-test 🤔 but, what u suggest?

[ozan956]

Hey @gastmaier, I created a PR for 6.18.31 and tested the artifact in #3489, It works for me/my case. So, I just switched to that approach and removed the thing from here. Thanks!