Evaluate Creator vs LAVA test frameworks

[Shpinkso]

As a embedded platform product owner, I want a reliable integration test framework on real hardware, so that automatic testing can be added to the CI pipeline Acceptance criteria

• Evaluation of the suitability and remaning effort for each framework to program and test clicker and ci40/clicker integration on real hardware, e.g.

[mtusnio]

Lava docker container - https://hub.docker.com/r/akbennett/lava-docker/ - can be used to avoid issues with dependencies.

[mtusnio]

There are a few steps we have to take here:

• Extend Lava framework with actions in the lava-dispatcher that allow for flashing & verifying the clicker. Then we can bundle up tests that just interpret the uart output from the clicker and return results. See the lava-dispatcher repo for sample actions. This then has to be used in a template for the clicker device.
• Fix creator-system-test-framework's tests to run both on virtualised setup & hardware. Some of them for now access the topologies explicitly which breaks compatibility with virtualised topology. Apart from that we need a hardware set-up to test if they work. Lava can be used to kick the test framework after flashing or in virtualised environment.
• Set up some PoC tests for the clicker and report results.