Fix for flaky GLIBC check on CI build

[miclegr]

Description

In the Combine JAR step of the CI build we check for shared libraries to require GLIBC<=2.27. We do that by dumping objects from shared libraries, grepping for GLIBC, removing unrelated string parts and sorting. But in this way we are catching also GLIBCXX entries, so ultimately the check depends on whether last matched object in the library is a GLIBC or GLIBCXX entry.

Also the test currently is failing if the maximum GLIBC/GLIBCXX required version by the library is strickly less than the maximum we allow.

Changes Made

• Improve check in the Combine JAR CI step.

Testing

Checklist

• My code follows the code style of this project.
• I have added and/or updated appropriate documentation (if applicable).
• All new and existing tests pass locally with these changes.
• I have run static code analysis (if available) and resolved any issues.
• I have considered backward compatibility (if applicable).
• I have confirmed that this PR does not introduce any security vulnerabilities.

Additional Comments

[psobot]

Great catch, thanks @miclegr!