GitHub Action: Check Code Coverage Bypass Statements and Eslint Disable Statements

[im-vedant]

Is your feature request related to a problem? Please describe.
Yes, the current workflow does not automatically detect or flag instances where:

1. Code coverage is bypassed using comments like /* istanbul ignore next / or / istanbul ignore file */.
2. ESLint rules are disabled using comments like /* eslint-disable / or / eslint-disable-next-line */.

These statements can bypass essential checks and affect code quality or test coverage reporting.

Describe the solution you'd like
Implement a GitHub Action that:

1. Scans for Code Coverage Bypass Comments:
   Detects /* istanbul ignore next /, / istanbul ignore file */, and other related comments in PRs.
   Fails the workflow if such comments are detected without proper justification.
2. Scans for ESLint Disable Comments:
   Detects /* eslint-disable /, / eslint-disable-next-line */, and similar comments in the code.
   Ensures that any disabled rule is logged and flagged for manual review.

[im-vedant]

@palisadoes Can you assign me this issue?

[github-actions]

Congratulations on making your first Issue! 🎊 If you haven't already, check out our Contributing Guidelines and Issue Reporting Guidelines to ensure that you are following our guidelines for contributing and making issues.