[Documentation][Release] Document how to identify issues that should be considered if a minor or patch release is done

[raulcd]

Describe the enhancement requested

In JIRA we had the ability to tag issues with multiple versions and we usually tagged them with possible patch and minor releases as well as with the newer versions.
In GitHub issues can have a single milestone and we create an issue that should be backported in case there is a new patch or minor release we currently don't have a process defined on how to "mark" this issue.
There is a backport-candidate label that could be used to do so but this should be documented. It should also be documented on the Release page in case of doing a patch or minor release so the Release Manager remembers to review those tasks.

Component(s)

Documentation, Release

[github-actions]

This issue has been marked as stale because it has had no activity in the past 365 days. Please remove the stale label or comment below, or this issue will be closed in 14 days. If this improvement is still desired but has no current owner, please add the 'Status: needs champion' label.