ci: Reduce redundancy by using workflows templates

[jlabatut]

Description

This PR aims to reduce redundancy in CI workflows by using workflows templates (e.g. : setting up Node/Yarn).

Issues Resolved

Closes #3603

Check List

• Update CHANGELOG.md
• Commits are signed per the DCO using --signoff

[jlabatut]

From what I understand (https://docs.github.com/en/actions/using-workflows/reusing-workflows#calling-a-reusable-workflow), the CI cannot find the template workflow since it is supposed to be called directly within a job, and not from within job steps.
But I cannot figure out how the next jobs could use the previously executed template job (setup Node/Yarn).

[kavilla]

Thanks for tackling this!

From what I understand (https://docs.github.com/en/actions/using-workflows/reusing-workflows#calling-a-reusable-workflow), the CI cannot find the template workflow since it is supposed to be called directly within a job, and not from within job steps. But I cannot figure out how the next jobs could use the previously executed template job (setup Node/Yarn).

Correct. What I would suggest is keeping the actual setup and execution of stuff together.

Not saying this is the only solution but one proposal can be like:

• build_and_test_workflow_template
• Then we pass flags like linux in

Another one could be like having

• unit_test_template
• integration_test_template
• functional_test_template
  That all setup their dependencies.

That then get called with flags from a build_and_test_workflow

We can also take it one step further and pull out the build and cypress tests.

• build_test
• cypress_test

[kavilla]

Converting to draft. Please feel free to open when changes made.

[ananzh]

@jlabatut Due to an extended period without updates, we're going to close this issue for now. We appreciate your contribution and understand that priorities and availability can change. Please feel free to reopen this issue when you have the opportunity to revisit it. Thank you for your understanding.