Use RegExp instead of micromatch.

[kontza]

Micromatch is more geared towards path matching and that doesn't really play well with e.g. Bitbucket style pull request messages like this example:

Pull request #323: feature/SMKY-1231 Responsiveness fixes

That forward slash breaks the old micromatch based implementation. The side effect here is that releaseRules patterns must now be compilable to regular expressions.

[kontza]

I left isString checks out on purpose:

• If src is not a string, then the RegExp will be a funky object which won't match a string.
• If object is not a string, then the re.test won't match.

[mbalc]

resolves https://github.com/semantic-release/commit-analyzer/issues/175 resolves #175

(I don't see the issue reference so let me attach it via a comment instead - useful to know what's the status of the issue, if it's being worked on)

[kontza]

Hi, I just merged upstream with my fork so that it should be compatible with it.

Please, could this be approved & merged.

Currently I need to do some funky s..t with a Python script in our CI/CD to overwrite the analyze-commits file with my version of it to have it build it properly without it dying on Bitbucket PR formatted messages (that we have all the time).