feat: Add JIRA issues parsing

[TheoGoudout]

When a JIRA issue is referenced in a commit, it is now possible to parse it. The JIRA issues will then be added to a dedicated section for each version.

[pawamoy]

Hi @TheoGoudout, thanks for the pull request 🙂

It's usually better to first open a new issue/discussion before a PR. I'm not a fan of how Jira support is "hardwired" into the code base. I don't think I'll want to maintain that 😕 I would have preferred an implementation based on ProviderRefParser, which I would have pointed you to in a discussion 😄

Also, are you aware we support Git trailers, which can be used to reference anything?

feat: Some new feature

Jira-123: https://link.to/jira/123

Such trailers are rendered in the changelog too: [Jira-123](https://link.to/jira/123) -> Jira-123.

[TheoGoudout]

You are right, I should have open an issue. I'll try and have a look at how to do it with ProviderRefParser.

I've seen that you support Git trailers but unfortunately, I don't think it would work with the way we do things in my workplace. Thanks, though.

You can close this PR if you want. I'll re-open one if I have enough time to do it yhe proper way.

[pawamoy]

Alright, thanks for your understanding!

It's very possible that ProviderRefParser is not flexible enough, since one can actually use Jira+GitHub, or Jira+GitLab, etc., so we'll have to discuss how to make it more flexible to allow combos (the class itself and its implementations, or how they're used higher up in the stack).

Quick note: another approach would be to allow users to hook into the parsing process, to augment commit data with their own logic. Worth discussing too.