Fix EfficacyThreshold and MutantCoverageThreshold check logic

[MadaManu]

Proposed changes

Threshold checks should fail if they fall short of the required value (i.e., less than the threshold). However, if the actual value matches the threshold exactly (e.g., 100 out of 100), it should not be considered a failure. The threshold has been met, so no error should be reported.

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices apply)

Checklist

• I have read the CONTRIBUTING doc
• Lint and unit tests pass locally with my changes (make all) - Addressed some linter issues reported on non changed files for this fix
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)
• Any dependent changes have been merged and published in downstream modules

Further comments

N/A

[MadaManu]

@k3rn31 can you please take a look at this?