Allow special handling for "skipped" breaking changes

[alerque]

On many of my projects, I choose to skip some scopes in the changelog, for example chore and refactor. This keeps the noise down and allows people to see features and fixes without the distraction of all the moving cheese.

However sometimes one of those commits will be marked as a breaking change (chore!: ....). These commits should not be skipped in the changelog. I found I catch these with a commit parser added early in the list. Unfortunately the other rules setting group titles then don't get applied.

commit_parsers = [
    { message = ".*!:", skip = false },
    { message = "^chore", group = "Miscellaneous Tasks", skip = true },
]

I can work it out by having duplicate rules for each group with breaking changes not being skipped and others being skipped, but it means a lot more rules that I would have expected.

I think there should probably be some top level support for handling breaking changes such that they can always override skip values.