Incorrect interpretation of trailling and leading spaces in version range parsing

[hj-lorenz]

Expected behavior

As a developer, I want the version range expression can be parsed correctly so that extra leading and trailling spaces won't cause problems.

Actual behavior

// this is acceptable, and it's actually fine
"versionRange": "[17, )"   (space between "," and ")")
"versionRange": "[17,21)"   (no leading or trailling spaces)

// this should also be acceptable but unfortunately you will encounter an incorrect interpretation
"versionRange": "[17,21 )"  (trailing space after "21")

From dependencies.json test with:

          "[2022-09,2023-09)": [
            {
              "tool": "java",
              "versionRange": "[17,21 )"
            }
          ],

we got this log:

Tool eclipse has 1 other tool(s) as dependency
Configured version of tool java is 11.0.26_4 but does not match version to install [17,21 ) - need to use different version from software repository.
Resolved version pattern [17,21 ) to version 21_35
Tool java has 0 other tool(s) as dependency
Version 21_35 of tool java is already installed at C:\projects\_ide\software\default\java\java\21_35
Version 2022-09 of tool eclipse is already installed at C:\projects\_ide\software\default\eclipse\eclipse\2022-09
Step 'Install eclipse' ended successfully.

It seems as if due to the extra space the max version was ignored in the version range.
This needs to be investigated.

Related issues

See PR #1020

Comments/Hints:

• leading spaces probably actual not really a problem but should also be deleted for interpretation to be left/right uniform
• Jörg: Maybe there is no bug in VersionRange but a bug in installToolDependencies that might just take the maximum/supremum of the range and then proceed with that version for the installation (21 -> 21_35). Further analysis and investigation required.

Affected version:

ide: 2025.02.001-beta-02_18_02-SNAPSHOT