When collecting patches and searching or validating fixed version, search all active version "lines"

[pombredanne]

When collecting patches and searching or validating fixed version, search all active version "lines", aka. branches that are maintained.

For instance we may find a patch that applies to v2.1.0 but the v1.0.0 branch may still be actively maintained and may need a patch. We can find and also check if it exists when it should.

Sometimes the patch may be missing, or forgotten by maintainers.

Reported by @ppkarwasz

[ppkarwasz]

This might be easier said than done, due to various ways projects prepare their releases.

For example in Log4j we use temporary release branches (release/*) to make a release and we replace the branch with a tag afterwards. Nevertheless all the code changes should be in the development branches (2.x and main).

Sometimes we decide to create an LTS and branches like 2.25.x appear.