Improve issue linking info

[John-Colvin]

trafficstars

the regex seems a bit restrictive, it would have been good to know this info.

@wilzbach relating to our discussion here

[dlang-bot]

Thanks for your pull request, @John-Colvin! We are looking forward to reviewing it, and you should be hearing from a maintainer soon.

Some tips to help speed things up:

• smaller, focused PRs are easier to review than big ones

• try not to mix up refactoring or style changes with bug fixes or feature enhancements

• provide helpful commit messages explaining the rationale behind each change

Bear in mind that large or tricky changes may require multiple rounds of review and revision.

Please see CONTRIBUTING.md for more information.

[wilzbach]

Hmm quoting from the Bugzilla paragraph below:

Using this syntax is also very important because for the changelog generation, the git history will be used. Thus only if the Dlang-Bot has detected an issue and commented on your PR it can become part of the changelog. In doubt, you can use e.g. Regex101 to validate your commit message.

Maybe simply linking or reordering the existing content?

[CyberShadow]

What's the status of this considering that we now use our own Bugzilla integration?