Validation of reusable device test workflows

[obbardc]

In #405, we reworked the test workflows to use reusable workflows which are shared across projects. This task is to validate that the new workflows trigger correctly in CI - verifying individual device test results is out of scope.

Since not all workflows could be tested from the branch or PR context, this task tracks the validation to ensure that each workflow triggers as expected after merging.

Test results (WIP)

Workflow	Links	Status	Comment
build-debian.yml	Workflow run	FINISHED	Some test failures; not sure if pre-merge tests are useful.
build-on-pr.yml (remote repo)	PR #661	FINISHED
build-on-pr.yml (local repo)	PR #595	FINISHED
build-on-push.yml	Workflow run	FINISHED	Some test failures; not sure if pre-merge is suitable here as it's on push to main.
build.yml	Workflow run	FINISHED
linux-arduino.yml	Workflow run	FINISHED	Some failures; not sure if pre-merge is useful here.
linux-mainline.yml	Workflow run	FINISHED	Some failures; not sure if pre-merge is useful here.
linux-next.yml	Workflow run	FINISHED	Some failures; not sure if pre-merge is useful here.
linux-qcom-7.2.yml	Workflow run	FINISHED	Tests OK; Need to discuss if it is worth running pre-merge tests on linux-*.yml workflows?
linux-qcom-laptops.yml	Workflow run	FINISHED

Out-of-scope (not using tests or are otherwise unrelated):

• build-overlay-deb.yml
• debos.yml
• efs-maintenance.yml
• known-failures.yml
• lint-on-pr.yml
• linux.yml
• linux-qcom-next.yml
• publish-results.yml
• qcom-preflight-checks.yml
• stale-issues.yaml
• static-checks.yml
• test-distro.yml
• test.yml
• test-pr.yml
• u-boot.yml

[obbardc]

OK; first set of failures:

• qcom-next: Error: Rendering test jobs for qcs8300-ride failed - I prepared a fix in fix(ci): update lava-test-plans for qcs8300-ride support #653

[obbardc]

Happy with the initial implementation of the new test workflows. Nothing left to action here; closing.