versionlock: Fix wildcards handling in add command

[m-blaha]

There’s a bug in how the dnf5 versionlock add <spec> command handles
package specifications when the spec contains a wildcard and matches
multiple package names with the same version (EVR). In such cases, only
the first package is considered, while the rest are quietly skipped.
For example there are three packages matching 'aws-checksums*' pattern,
but only one is actually locked:

❯ dnf repoquery 'aws-checksums*'
Repositories loaded.
aws-checksums-0:0.2.2-1.fc40.i686
aws-checksums-0:0.2.2-1.fc40.x86_64
aws-checksums-devel-0:0.2.2-1.fc40.i686
aws-checksums-devel-0:0.2.2-1.fc40.x86_64
aws-checksums-libs-0:0.2.2-1.fc40.i686
aws-checksums-libs-0:0.2.2-1.fc40.x86_64

❯ dnf versionlock add 'aws-checksums*'
Repositories loaded.
Adding versionlock on "aws-checksums = 0.2.2-1.fc40".

With this patch, each group of packages with the same name is handled
separately, ensuring that all the packages are correctly locked:

❯ dnf5 versionlock add 'aws-checksums*'
Repositories loaded.
Adding versionlock on "aws-checksums = 0.2.2-1.fc40".
Adding versionlock on "aws-checksums-devel = 0.2.2-1.fc40".
Adding versionlock on "aws-checksums-libs = 0.2.2-1.fc40".

For: #1895

[kontura]

This looks good, I have created a simple test here: rpm-software-management/ci-dnf-stack#1620

I am curious, I see this doesn't really work with architectures and the docs do say at the beginning that it works with set of names and versions for packages, on the other hand they specify package-spec as an argument.
From the description of the add subcommand I would expect that
versionlock add name*.x86_64
would work just for x86_64.

Is the support for architectures being considered?