Separate Code Coverage into Dedicated Workflow

[AnasBahr]

The current workflow (Build & Test Fedora) includes both build/test and coverage generation. To improve clarity, performance, and modularity, we should move all coverage steps into a standalone workflow.

Motivation:
The existing workflow runs build, testing, and coverage in a single job, which makes it longer and harder to debug. Coverage requires a separate build configuration (-DCOVERAGE=ON), which can be isolated. By decoupling coverage from build and test, we can rerun coverage jobs independently, reduce CI runtime, and maintain a cleaner structure between test validation and metric collection.

Acceptance Criteria:

• The Build & Test Fedora workflow runs without any coverage logic.
• A new Coverage (Fedora) workflow runs automatically after completion.
• Both pytest and ctest coverage data are uploaded to Codecov.

[leonardocarreras]

Hi Anas! Your solution and approach looks reasonable to me