Support ruby style requirements as gradle requirements

[jonabc]

What are you trying to accomplish?

NOTE: Support ruby-style version requirements that are created from
PR ignore conditions

This change addresses the comment found in both gradle and maven requirement types

A requirement like > 1.2.3+0.1.1 can be provided as part of an ignore condition from a chat command like @dependabot ignore. The string contains a dynamic version and without this change will end up being translated to ~> > 1.2.3+0.1.1 with dual operators making it an invalid requirement.

If a caller has already provided an operator as part of the requirement, it seems like we should be respecting that and not overwriting it. The java version classes seems to work fine with comparisons between dynamic versions.

Anything you want to highlight for special attention from reviewers?

Is there any case where a dynamic requirement string could be used with a non-gradle requirement or version class? If Gradle's requirement class ever passes off the requirement as a string to Gem::Version for example, this change would be incorrect.

How will you know you've accomplished your goal?

@dependabot ignore works on a gradle or maven dependency with a dynamic version

Checklist

• I have run the complete test suite to ensure all tests and linters pass.
• I have thoroughly tested my code changes to ensure they work as expected, including adding additional tests for new functionality.
• I have written clear and descriptive commit messages.
• I have provided a detailed description of the changes in the pull request, including the problem it addresses, how it fixes the problem, and any relevant details about the implementation.
• I have ensured that the code is well-documented and easy to understand.