Expose secure boot testing features via matrix input

[klutchell]

Some device types (generic-armd64) need to run the test
suites twice for the same base image, once with secure boot
vars enabled in Leviathan, and once without.

Rather than run the suites in series, or require building the
image twice, we can allow the test matrix to define separate runs
for the two modes.

[rcooke-warwick]

https://github.com/balena-os/leviathan/blob/master/action.yml#L46

There is a conflict here - with the SB matrix it tries to make artifacts with the same name amd fails

[vipulgupta2048]

@rcooke-warwick Do you have a run where the conflict appears. With Kyle's change, it seems we won't be doing a normal run when secureboot will be enabled. Hence, yes the artifacts could be better named to exactly show the secureboot run but there won't be other artifacts present?

[rcooke-warwick]

There are other artifacts present because there is a SB and non SB version of the tests run, and both produce artifacts with the same name

E.g https://github.com/balena-os/balena-generic/actions/runs/11216427427/job/31184440638?pr=530

>Run actions/upload-artifact@50769540e7f4bd5e21e526ee35c689e35e0d6874
With the provided path, there will be 4 files uploaded
Artifact name is valid!
Root directory input is valid!
Error: Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run

We need another variable in the artifact name to differentiate it

[rcooke-warwick]

We also still need to figure out why the SB enables DUT never comes online , even after the 4G memory being enabled

[klutchell]

There are other artifacts present because there is a SB and non SB version of the tests run, and both produce artifacts with the same name

E.g https://github.com/balena-os/balena-generic/actions/runs/11216427427/job/31184440638?pr=530

>Run actions/upload-artifact@50769540e7f4bd5e21e526ee35c689e35e0d6874
With the provided path, there will be 4 files uploaded
Artifact name is valid!
Root directory input is valid!
Error: Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run

We need another variable in the artifact name to differentiate it

This fix will have to be in the Leviathan workflow to generate unique artifact names -- ideally unique with a bunch of properties, like machine, signed/unsigned, worker type, etc. @vipulgupta2048

[rcooke-warwick]

There are other artifacts present because there is a SB and non SB version of the tests run, and both produce artifacts with the same name
E.g https://github.com/balena-os/balena-generic/actions/runs/11216427427/job/31184440638?pr=530

>Run actions/upload-artifact@50769540e7f4bd5e21e526ee35c689e35e0d6874
With the provided path, there will be 4 files uploaded
Artifact name is valid!
Root directory input is valid!
Error: Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run

We need another variable in the artifact name to differentiate it

This fix will have to be in the Leviathan workflow to generate unique artifact names -- ideally unique with a bunch of properties, like machine, signed/unsigned, worker type, etc. @vipulgupta2048

balena-os/leviathan#1243 here is a shot at that