VersionRange for root features is too tight when expanded version given

[laeubi]

Currently the (disabled by default) requirement for a root feature uses an exact version range when the feature version is expanded (e.g. Tycho) but the purpose of a root feature is that it can be updated what such a strict range makes it impossible (if activated).

This now adds a new IVersionRangeAdvice that allows to modify the result of a product included requirements version range.

[github-actions]

Test Results

    9 files  ±0      9 suites  ±0   29m 47s ⏱️ -30s
2 196 tests ±0  2 192 ✅ ±0   4 💤 ±0  0 ❌ ±0 
6 678 runs  ±0  6 667 ✅ ±0  11 💤 ±0  0 ❌ ±0 

Results for commit 0424619. ± Comparison against base commit 4426f86.

♻️ This comment has been updated with latest results.

[merks]

Looks fine.

I questioned if we should upper bound with the next major version, but I do feature really respect semantic versioning and even if they do, what safety would this really buy us? So I think only a lower bound is okay.

[laeubi]

I think the best would be if one can configure it in the product editor like it is possible with feature dependencies, this would probably be even better than the current "root feature" approach. But that's more for a future enhancement.