ci(spread): add reusable workflow for Spread tests

[cjdcordeiro]

Proposed changes

This PR introduces a new reusable GitHub workflow for running Spread tests.

Each branch will have its own spread.yaml configuration, and this workflow will be called from the branches, on every PR.

The tests shall only run for:

• the SDFs which are added or modified
• the tests which are added or modified

Testing

Tested the execution of this workflow here:

• Ubuntu 24.04 spread cjdcordeiro/chisel-releases#11 (with additional mock commits to ensure the logic works when filtering the added and modified files)
• Rocks 1262/add spread tests 24.04 test cjdcordeiro/chisel-releases#13

Checklist

• I have read the contributing guidelines
• I have already submitted the CLA form

[letFunny]

Thanks Cris, it is looking very good! From the linked PRs I am missing the use case where the spread tests already exists and changing the SDF triggers the integration test (i.e. changed-slices triggering instead of changed-tests).

[cjdcordeiro]

Thanks Cris, it is looking very good! From the linked PRs I am missing the use case where the spread tests already exists and changing the SDF triggers the integration test (i.e. changed-slices triggering instead of changed-tests).

Thanks.

As for that use case, it's this one here: https://github.com/cjdcordeiro/chisel-releases/actions/runs/9905003363/job/27363593631?pr=11#step:8:27

From the logs you can see the SDF being considered as a trigger for that test. It just so happens that the test itself is also a trigger, cause it is also being created for the first time.

[rebornplusplus]

Looks good to me, thank you!

Just one quick question about using less distinct actions.