raise code coverage to 100%

[reactive-firewall]

Coverage is below 100% still.

The goal of this issue is to raise the overall test coverage of code in the project's multicast module (e.g. code located in "multicast/*.py") to above 99% (basically 100% when rounding)

Work on this goal is to be tracked by this GH issue.

Notes:

• Development branch: testing-coverage
• Tests in the CI job "COVERAGE" and "INTEGRATION" report their coverage to the service codecov.
• Testing Naming guidelines are detailed in CEP-9
• Test code should be documented as per CEP-7

[coderabbitai]

Technical Debt: Coverage Reporting Improvements

As discussed in PR #75, the current coverage reporting commands have been a source of significant code churn historically. While improvements are desirable, they are being deferred to future PRs due to their complex history and potential for introducing instability.

Alternative approaches to consider in the future:

1. Log warning messages when non-zero exit codes occur in coverage reporting.
2. Implement a fallback mechanism to generate partial coverage reports when issues arise.
3. Fail the build process if critical coverage reporting issues occur.

Rationale for holding off on changes:

• Historical complexity and churn associated with these commands.
• Need to maintain current stability while acknowledging the importance of coverage reporting.
• Balancing the value of coverage reporting with the project's current needs and constraints.

This issue will serve as a reminder to revisit and potentially implement these improvements in future development cycles.