Adds support for regex in autolinks

[felipecrs]

Description

Adds support for autolink references based on regular expression for more advanced use cases, while keeping backwards compatibily with the existing prefix-based cases.

Additionally, it refactors the Gerrit autolinks to leverage the new option:

• Closes Make autolinks more sophisticated #1903
• Closes Regular expressions in autolinks #1314
• Closes Bugtraq Support For Issue Trackers #1121
• Fixes Gerrit: parse change-ids in the whole message body, not only in the footer #2251

Checklist

• I have followed the guidelines in the Contributing document
• My changes follow the coding style of this project
• My changes build without any errors or warnings
• My changes have been formatted and linted
• My changes include any required corresponding changes to the documentation (including CHANGELOG.md and README.md)
• My changes have been rebased and squashed to the minimal number (typically 1) of relevant commits
• My changes have a descriptive commit message with a short title, including a Fixes $XXX - or Closes #XXX - prefix to auto-close the issue that your PR addresses

Extras:

• Make changes to the embedded settings browser (help welcome)
• Properly handle escaped markdown (and probably HTML) matching

[felipecrs]

This produces:

Code_McgfIrbujZ.mp4

[felipecrs]

Update: we can probably use regexp-tree to parse the regex and escape it properly for markdown and html.

[felipecrs]

Ok, this is now working. The implementation may be a little rough though.

You can test with the following repo:

git clone https://review.gerrithub.io/felipecrs/gerrit-jenkins

And the last commit. It comes with a settings.json like:

{
  "gitlens.autolinks": [
    {
      "regex": "(JENKINS-[0-9]+)",
      "url": "https://issues.jenkins.io/browse/<num>"
    }
  ]
}

Demo:

Code_3ute0TidEL.mp4

[ajmath]

This would be awesome and open up matching on JIRA ticket ids in branch names, ex: feat_proj_123

[ahochsteger]

@eamodio, any chance to get that merged?
I just wanted to configure Gitlens once for all Jira projecs as well and was surprised that this was not working.
I mentioned you, since you originally suggested to provide a PR here: #1314 (comment) which @felipecrs already seems to have solved.

[sadasant]

I'm wondering if it would be too hard to achieve the same result without having to add a new dependency to vscode-gitlens 🤔

regexp-tree is really cool, nonetheless.

[felipecrs]

I tried very hard and could not find any other way sadly.

Actually it took me a long way to reach this state even.

lol

[hongtron]

Could we clarify what changes must be made to this implementation in order to get it merged (other than resolving conflicts)? Is the added dependency a dealbreaker, or could it be acceptable as an interim solution? Would love to see this functionality hit main!