Fix branches logic wrt devel version in latest branch

[AMDmi3]

Report against gtk project was filled: latest 3.x version 3.24.28 is considered outdated for some repositories.

The current logic was intended to work as follows in this case: "mark 3.x version legacy (instead of outdated) if it's greatest in 3.x and there's also 4.x version in the same repo". In other words,

• 3.24.27 - always outdated, not latest in 3.x
• 3.24.28 in absence of 4.x versions - outdated (indication of that there's new version from a major branch)
• 3.24.28 in presence of 4.x versions - legacy (is latest 3.x, and status for 4.x is processed separately)

However, this logic only considers stable versions in the 4.x branch, so it would consider latest 3.x 3.24.28 outdated if the only 4.x version packaged is not stable (e.g. 4.1, while stable is 4.0).

This doesn't look consistent and fair, as 3.x version should not care of WHICH 4.x version is packaged

• as long as there IS any 4.x version, there's no longer need need to indicate that there's new major branch
• it currently does not care whether the 4.x version is outdated or not, it shouldn't care whether it's devel or not
• in practice another branch may be maintained by a different person, so this problem may not be directly fixable by 3.x maintainer