Add twister workflow

[MarkoSagadin]

Description

This PR adds twister workflow and make commands that are used in it.

Twister workflow can:

• run twister to build and execute all projects in tests/ dir
• create test report
• create coverage report

Relevant documentation was also updated.

Related: https://github.com/IRNAS/irnas-workflows-software/pull/8

Areas of interest for the reviewer

Documentation in the tests/ and make commands.

Checklist

• [x] My code follows the [style guidelines] as defined by IRNAS.
• [x] I have performed a self-review of my code.
• [x] My changes generate no new warnings.
• [x] I added/updated source code documentation for all newly added or changed functions.
• [x] I updated all customer-facing technical documentation.

After-review steps

• I will merge PR by myself.

[style guidelines]: https://github.com/IRNAS/irnas-guidelines-docs/blob/main/docs/developer_guidelines.md

[MarkoSagadin]

Current dependencies on/for this PR:

• main
  • PR #8 👈

This comment was auto-generated by Graphite.

[github-actions[bot]]

Coverage after merging feature/twister into main will be

75.00%

Coverage Report

File	Stmts	Branches	Funcs	Lines	Uncovered Lines
lib/example_lib
example_lib.c	71.43%	50%	100%	75%	10, 14

[github-actions[bot]]

Coverage after merging feature/twister into main will be

75.00%

Coverage Report

File	Stmts	Branches	Funcs	Lines	Uncovered Lines
lib/example_lib
example_lib.c	71.43%	50%	100%	75%	10, 14

[MarkoSagadin]

@TjazVracko

Could we get these changes as a patch so I can apply them to existing projects?

Sure, just add .patch to the PR url and you can download the raw file. Like so: https://github.com/IRNAS/irnas-zephyr-template/pull/8.patch

Also, what happens if my project does not have a tests folder? I don't want CI checks to fail in that case. In that case I would suggest to not apply the patch.