Allow multiple parsers for skipped/non-skipped commits

[orhun]

Is your feature request related to a problem? Please describe.

From PR #114:

Note that during testing, one caveat was discovered: If a commit is matched by one parser, it can't be matched by any other. That means if a breaking commit was prevented from being skipped, it won't become part of any other group. Maybe it is worth to think about allowing multiple parsers for commits in an hierarchical order?

Describe the solution you'd like
Allow commits to be parsed by multiple commit_parsers (if skipped).

Describe alternatives you've considered
None.

Additional context
I think this issue needs some brainstorming. Let me know if you want to tackle it!

[tonny008]

I need this feature even it is not skipped.

I thought below config will work. but it NOT. only the first match takes effect.

  [
{ message = "(scope)", scope = "Fancy Scope" },
{ message = "^feat", group = "<!-- 0 -->🚀 Features" }
]

to make it work. i need below parser. it is tedious with many scopes and groups.

[{ message = "^feat\(scope\)", scope = "Fancy Scope", group =  "<!-- 0 -->🚀 Features"}]