Fix: Ensure Scope Filtering is Enforced Correctly

Resolves#1215

Purpose

This PR ensures thatscope filtering logic is correctly applied whenallowed_scopes is configured inConventionalCommitParserOptions. Previously, commits without a scope were incorrectly bypassing the filtering, and commits with no allowed scopes defined were still being evaluated unnecessarily.

Rationale

1. Ifallowed_scopesis not defined, the filtering logic should be skipped entirely to maintain the existing behavior.
2. Ifallowed_scopesis defined, the commitmust have a valid scope that is explicitly allowed.
3. If a commithas no scope, itshould not be allowed whenallowed_scopes is configured.

This change ensures a strict enforcement of scope filtering while keeping backwards compatibility whenallowed_scopes is not set.

How did you test?

• Added unit tests to verify:

  • Commitswith allowed scopes pass the filter.
  • Commitswith disallowed scopes are correctly rejected.
  • Commitswithout a scope arerejected whenallowed_scopes is enabled.
  • Commitswithout anallowed_scopes definition behave as they currently do.

• Ran the test suite and verified that existing functionality remains unchanged for users who do not configure scope filtering.

How to Verify

1. Runpytest to ensure all tests pass.
2. Use theConventionalCommitParser with different configurations:
   • Noallowed_scopes: Behavior remains unchanged.
   • allowed_scopes defined: Only commits with matching scopes should be allowed.
   • Commit with no scope: Should be rejected whenallowed_scopes is defined.

PR Completion Checklist

• Reviewed & followed theContributor Guidelines
• Changes Implemented & Validation pipeline succeeds
• Commits follow theConventional Commits standard
  and are separated into the proper commit type and scope (recommended order: test, build, feat/fix, docs)
• Appropriate Unit tests added/updated
• Appropriate End-to-End tests added/updated
• Appropriate Documentation added/updated and syntax validated for sphinx build (see Contributor Guidelines)