Description

This PR adds documentation clarifying how prerelease versions work with semver ranges in npm install commands.

Changes

• Added a 'Prerelease versions' section under version range documentation
• Explained that prereleases must be explicitly specified in ranges
• Clarified that prerelease versions are tied to specific version triples
• Provided examples showing how to match prereleases for patch vs major versions

Fixes

Closes #7851

Context

Users were confused about why version ranges like ^1.2.3-beta.1\ don't match \1.3.0-beta.1\ and why
pm outdated\ doesn't suggest updating from one prerelease to another with a higher patch version. This is by design in semver - prereleases are scoped to a specific major.minor.patch triple. The documentation previously didn't explain this behavior, leading to confusion about whether it was a bug.

The added documentation clarifies:

1. Prerelease versions must be explicitly included in ranges (they're not matched by default)
2. A range like ^1.2.3-beta.1\ only matches prereleases for \1.2.x\ versions
3. To match all prereleases for a major version, use ^1.0.0-0\

Type of Change

• Documentation update