Close Matching Issues on New Release.yml

[Marco-9456]

Description

This workflow triggers when a new release is published and performs the following tasks:

• Checks out the code of the latest release.
• Sets up GitHub CLI for the job.
• Iterates over all open issues with labels matching the version of the new release.
• Checks the labels of the issues, and if an issue has either "bug" or "enhancement" label,
  adds a comment to the issue stating either "Fixed in [version]" or "Added in [version]" respectively, with a link to the new release.
• Closes the issues and counts the number of bug fixes and enhancements introduced in the new release.

Requirements

1. The issues in the repository should be labelled with the version number that they are expected to be resolved in.

2. A GitHub Personal Access Token (PAT) with the necessary permissions is required. This PAT should be stored in the repository secrets as PERSONAL_ACCESS_TOKEN.

Usage

This workflow runs automatically when a new release is published in your GitHub repository. To ensure its functionality:

1. Whenever a user create an issue that you want to fix/implement, label it with the version number in which you expect it to be resolved.

2. When the release is published, this workflow will automatically run, checking and closing all issues labelled with the release version, for example v1.10.