fix: minVersion returns the true minimum for > in includePrerelease mode

[spokodev]

What

minVersion returns "the lowest version that can possibly match the given range", but for a >X.Y.Z bound in includePrerelease mode it skips the lowest prerelease of the next version:

semver.minVersion('>1.0.0', { includePrerelease: true }) // 1.0.1

1.0.1-0 also satisfies >1.0.0 under includePrerelease and is lower than 1.0.1:

semver.satisfies('1.0.1-0', '>1.0.0', { includePrerelease: true }) // true
semver.lt('1.0.1-0', '1.0.1')                                      // true

so 1.0.1 is not the minimum.

Root cause

For a > comparator that already carries a prerelease, minVersion appends .0 to reach the lowest prerelease (>1.0.0-0 → 1.0.0-0.0). The plain >X.Y.Z branch only did patch++ and never considered prereleases — even when includePrerelease puts them in scope.

Fix

After bumping the patch for a prerelease-less > bound, append the -0 prerelease when the range includes prereleases, so >1.0.0 yields 1.0.1-0. Default (non-includePrerelease) mode is unchanged — >1.0.0 still yields 1.0.1.

Tests

Added ['>1.0.0', '1.0.1-0', { includePrerelease: true }] and ['>2 || >1.0.0', '1.0.1-0', { includePrerelease: true }]. Both fail on main and pass with the fix; the existing default-mode case ['>1.0.0', '1.0.1'] is untouched and the ranges suite stays green.