Allow the Title of e.g. a Squash Commit to not be a Conventional Commit

Thanks for stopping by to let us know something could be better!

**Is your feature request related to a problem? Please describe.**
Let's say i wanna merge a PR. The PR contains multiple fixes, features, and also a refactor!, which is a BREAKING CHANGE. Now, what you have to do now is to use any commit of those as the merge commit title. So when you look into your history, you see a specific commit as the title, but actually in its description there are many other fixes and features which also deserve to be mentioned or are part of a bigger picture that was merged.

**Describe the solution you'd like**
The title of a merge commit should be allowed to not be conventional so i can use this to describe the minor fixes and features i added in that squash commit as a whole for a better, more informative git history.

**Describe alternatives you've considered**
Actually, i found out that you can do an unconventional commit title and get all the fixes and features in the commit description still listed in the Changelog. But this works only for said types. The refactor! commit with a BREAKING CHANGE is not listed at all, and the version change also is just a minor one.
My guess is, that release please kind of panics because of the malformed commit title, So i think there needs to be some logic in the release please code to actually allow this.