Should we introduce a code coverage workflow to get some insights and metrics for on how efficiently we are testing?

Implementing coverage in CMake has to be done manually, i.e. there is no switch that will work this automatically and we have to deal with the fact that some files are produced by fypp and ensure that the coverage reports are generated and uploaded for the actual source and not the preprocessed files.

This would probably also be limited to a single GCC workflow?