Add rule to ban dependencies with specific version qualifiers

[ms-f10]

New feature, improvement proposal

I would like to request a new enforcer rule (or enhancement to existing rules) that can ban dependencies based on version qualifiers/suffixes, independent of the specific version number.

Current Limitation:

The BannedDependencies rule currently cannot match version qualifiers flexibly. I attempted the following configuration:

<bannedDependencies>
    <excludes>
        <exclude>a.b.c*:*:*-a*</exclude>
        <exclude>a.b.c*:*:*-m*</exclude>
        <exclude>a.b.c*:*:*-rc*</exclude>
    </excludes>
</bannedDependencies>

However, based on the ArtifactMatcher implementation, the version field does not support wildcard matching for qualifiers in this way.

[cstamas]

I think you want "no preview" versions:
https://github.com/maveniverse/toolbox/blob/09e98a04d12a540f33c113b32955f094dbb27ca7/shared/src/main/java/eu/maveniverse/maven/toolbox/shared/ArtifactVersionMatcher.java#L110-L115

"Preview" qualifiers are defined here:
https://github.com/apache/maven-resolver/blob/maven-resolver-1.9.x/maven-resolver-util/src/main/java/org/eclipse/aether/util/version/GenericVersion.java#L183-L187

[ms-f10]

Basically, but i still want to be able to control on which groupId i want to enforce the banning of such preview versions.