[RFE] Implement proper dependency version boundary ranges

[jmle]

In konveyor, dependency condition versions are specified using lowerbound and upperbound properties (see docs). Both bounds are included, this is, versions will be [less|greater] or equal than the number.

It would be good to have a mechanism that would allow things like:

• Match on versions up to, but not including, 5.0: (,5.0)
• Match on versions from 4.0 to 5.0, both included: [4.0, 5.0]
• Match on versions from 4.0 (not included): (4.0,)
• ...and so on

This is quite convenient for rule authors, as there is no need to check versions in repositories. In konveyor, version numbers can only be specified with a range including the version specified. This makes the rule author have to look for the previous version number if he or she does not want to include a version up to which the rule shouldn't match (open range).

[konveyor-ci-bot]

This issue is currently awaiting triage.
If contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members.

[rromannissen]

+1