No additional labeling nor project assigning for release pull requests

[mondeja]

We started adding new icon Issues or pull requests for adding a new icon and update icon/data Issues or pull requests regarding icons that are outdated, this can be the SVG or color or both labels to release pull requests in #10785 (see here). After some digging, I think that the change was introduced by #10726, but I'm not sure.

Anyways, if we're targetting master base ref we don't need to assign to a project nor add labels to that pull request because we can assume that is a special pull request.

When this PR is merged I'll remove those labels of the release pull requests for previous releases.

[LitoMore]

I'll remove those labels of the release pull requests for previous releases.

@mondeja Updating merged PRs may cause an issue with the inconsistent release note.

• Inconsistencies of icons includes in releases and release notes release-action#83

[mondeja]

I've removed all labels from previous release Pull requests that released a new version pull requests except the release Pull requests that released a new version one. That issue happens with pull requests that has not been included in the last release, which are the ones that the release action uses to generate the release note.