A constraint with a pre-release and a feature suffix matches nothing #151

Description

A version constraint that combines a numbered pre-release with a feature suffix matches nothing, even the release with exactly that tag.

Constraint cuts only a whole --separated stability keyword off the suffix, so beta.1-feature stays the feature suffix. Version reads beta.1 as the stability and keeps only feature as the suffix. The str_contains() check then never passes.

Expected: 3.5.0-beta.1-feature matches v3.5.0-beta.1-feature and nothing else, the same way 3.5.0-beta.1 names one release after #150.

Steps to reproduce

use Internal\DLoad\Module\Version\{Constraint, Version};

Constraint::fromConstraintString('3.5.0-beta.1-feature')
    ->isSatisfiedBy(Version::fromVersionString('v3.5.0-beta.1-feature')); // false

The last row is the workaround: drop the pre-release number and give the stability with @.

Additional context

• Same result on 1.x before feat(version): match constraints with DLoad's own version ordering #150, so it is not a regression from it.
• ConstraintTest::provideValidConstraints ('base with multiple dashes') pins the current parse of ^2.12.0-alpha.1-feature: feature suffix alpha.1-feature, stability Preview.
• feat(version): match constraints with DLoad's own version ordering #150 recognises a pre-release only when it ends the constraint (X.Y.Z-<keyword>N); a fix would extend that to a pre-release followed by -<feature>.