GitHub action for code coverage

[SuhashiniNaik]

This GitHub Action automates the generation and publishing of code coverage reports of the modules. It captures code coverage data using lcov, filters out third-party, mock files, gtest folders and system libraries.
Then it generates an HTML report that is deployed to GitHub Pages.

Changes made:
Added code-coverage.yml
Added CodeCoverage.cmake
Made changes in CMakeLists.txt

[marcmo]

rather than exclude a whole list of locations, only exclude the mock/test patterns and instead use options like:

	•	--directory: Specifies the directory containing .gcda and .gcno files.
	•	--capture: Captures coverage data.
	•	--include/--extract: Includes files matching specific patterns.
	•	--remove: Excludes files matching specific patterns.
	•	--no-external: Excludes coverage data for files outside the specified directory.

[SuhashiniNaik]

Yes Oliver, I have excluded the mock/test patterns but I also had to exclude 3rd party files because they were not getting excluded by using --no-external command in the latest commit. It works for excluding system libraries though

[marcmo]

since we run the tests in this action, we should remove the test execution in the build.yml file

[ThoFrank]

I think this action should be split into parts. Similar to the documentation action:

1. Build the coverage, zip it and upload the artifact. Should only run on PR's. This way you can still view the output by downloading the zip.
2. Download the zip, unpack it and publish it. Should only run on push to master (and as a dependency to action 1).

Action 2 could be combined with the doc publish action.

Additionally action 1 could also be integrated into the release workflow. But probably this should be done in another PR, because the permissions in the release workflow need to be fixed.

[marcmo]

@ThoFrank that change makes sense...we only want to re-publish the coverage results when a commit is done to the main branch. where is the zip file stored and how can contributors access it?

@SuhashiniNaik Please also squash your commits to the feature branch.

[ThoFrank]

@marcmo Right now the link is only available in the action log. But we could look into posting the link as a comment to the pr.

For an example see here -> Upload docs

[vladyslavmarkovaccenture]

Since we don't have debug symbols in the debug build now the code coverage info might be imprecise. This is fixed in #23 along with failing unit test. I suggest merging it first.

[marcmo]

LGTM