Treat x.y.999-SNAPSHOT as snapshot version

[rsvoboda]

Summary

Treat x.y.999-SNAPSHOT as snapshot version

Port of one change from #920
To cover cases like 3.2.999-SNAPSHOT and whatever future 3.y.999-SNAPSHOT

Please check the relevant options

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Dependency update
• Refactoring
• Breaking change (fix or feature that would cause existing functionality to change)
• This change requires a documentation update
• This change requires execution against OCP (use run tests phrase in comment)

Checklist:

• Example scenarios has been updated / added
• Methods and classes used in PR scenarios are meaningful
• Commits are well encapsulated and follow the best practices

[michalvavrik]

I will temporarily add DON'T MERGE label for I need #928 to be based on the latest main, otherwise release workflow breaks.

[michalvavrik]

Not that I was asked, but I approve :-)

Personally I'd use endsWith for it only iterate over (the worst case) word.length() while contains goes from start of the tested string (so it can't leverage offset). But it doesn't really matter. Maybe you want to match some other 999-SNAPSHOT versions with suffix too?