feat(config): support changing commit scope with commit_parsers

[ofsahof]

Description

I followed the instructions :)
Some new test cases are missing but I'll add as soon as possible

Motivation and Context

For overriding commit scope.

resolves #50

How Has This Been Tested?

Current tests are passing. New tests are missing.

Screenshots / Output (if appropriate):

Types of changes

• Bug fix (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 change)
• Documentation (no code change)
• Refactor (refactoring production code)
• Other

Checklist:

• My code follows the code style of this project.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

[codecov-commenter]

Codecov Report

Merging #94 (1885227) into main (7d0786c) will increase coverage by 1.08%.
The diff coverage is 68.75%.

@@            Coverage Diff             @@
##             main      #94      +/-   ##
==========================================
+ Coverage   39.08%   40.15%   +1.08%     
==========================================
  Files          15       15              
  Lines         947      969      +22     
  Branches      249      252       +3     
==========================================
+ Hits          370      389      +19     
- Misses        453      456       +3     
  Partials      124      124              

Impacted Files	Coverage Δ
git-cliff-core/src/config.rs	16.67% <0.00%> (-0.28%)	⬇️
git-cliff-core/src/commit.rs	69.66% <50.00%> (+0.23%)	⬆️
git-cliff/src/changelog.rs	74.88% <100.00%> (+1.69%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7d0786c...1885227. Read the comment docs.

[orhun]

Haven't tested it but looks good. Can you run cargo fmt and cargo clippy and update the code? Also, I think README.md could be updated about this change.