Allow configurable list of conventional commits

[arielvalentin]

There are cases where we want to release a new version of gems for changes that may not be considered new features or fixes.

Some examples I can think of where the release:

• When updating production runtime dependencies via Dependabot: chore
• Internal refactorings, which do not change the external behavior: refactor

There is also some degree of granularity in some cases where we do not want to generate a release, e.g. chore(dev-deps), so it may be helpful to allow users to customize what attributes would trigger a release and if it would constitute a major, minor, or patch release.

toys/.toys/release/.lib/release_requester.rb

Line 128 in 5d3272d

match = /^(fix|feat|docs)(?:\([^()]+\))?(!?):\s+(.*)$/.match(title)

[dazuma]

We can certainly do this. However, I think this should be combined with being more descriptive in the conventional commit tags we use. For example, if we want production runtime updates to be significant, they should probably be something like deps: instead of chore:, and then we can map those to, say, patch releases. (And dev deps could either remain chore: or be something like devdeps:.) I wonder if we can configure dependabot to give us better tags.

I'll start with supporting a configurable mapping between conventional commit tags and semver types, and see how far we can get with that.