Refine breaking change detection

The Problem

By accident, I triggered a breaking change for a package since the commit message body stated:

fix: add esnext entry point
because the package.json did not provide one until now, breaking builds when trying to use this in a hops setup.

I can see people using the word "breaking" in other instances as well, e.g. "using the grid to prevent the interface breaking into two lines". This shouldn't trigger a breaking change.

Proposed solution

I'd remove the i in the Regex searching for breaking changes here:

rlsr/src/read/getParsedCommitMessages.js

Line 5 in e742f7e

const BREAKING_REGEXP = /BREAKING/i;

Fixed in #38