Add links to all issues in the 3.7.2 section of the changelog

[rodrigoprimo]

Description

This PR adds links to all issues in the 3.7.2 section of the changelog. I also checked for grammar or Markdown errors, but I did not find anything.

Related issues/external references

Part of #244

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
  • This change is only breaking for integrators, not for external standards or end-users.
• Documentation improvement

PR checklist

• I have checked there is no other PR open for the same change.
• I have read the Contribution Guidelines.
• I grant the project the right to include and distribute the code under the BSD-3-Clause license (and I have the right to grant these rights).
• I have added tests to cover my changes.
• I have verified that the code complies with the projects coding standards.
• [Required for new sniffs] I have added XML documentation for the sniff.

[jrfnl]

Thanks @rodrigoprimo ! Great start for that issue.

[rodrigoprimo]

Thanks for the quick review, @jrfnl! For future PRs for that issue, do you prefer that I create one PR for each release, or is it fine to group a few releases in a single PR? I think that, especially for smaller releases, grouping them should allow us to move faster and will not make the review process significantly harder. That being said, I'm happy to proceed as you prefer.

[jrfnl]

Thanks for the quick review, @jrfnl! For future PRs for that issue, do you prefer that I create one PR for each release, or is it fine to group a few releases in a single PR?

@rodrigoprimo Thanks for asking. I'm fine with grouping the updates for multiple releases in a single PR, as long as a note is left on the #244 ticket to "claim" the releases which are being worked on, to prevent duplication of efforts by multiple people.

Also, I know from my own experience creating #243, that it can get tedious working on these kind of updates for too long at a time, so it's fine to do a few releases, commit & PR and continue another time with other releases.
(though #243 probably involved a lot more research than will be needed for the remaining work)

[rodrigoprimo]

Sounds good to me. I will try to do a few per week, and I will make sure to leave a comment in the issue claiming the releases before starting.

[jrfnl]

Just noticed while reviewing your next PR that the links all use issues and are not always the canonical link. While I realize that currently works in GitHub, that hasn't always been the case, so I prefer to err on the side of caution and to always use the canonical link.