Product precedence check does not consider products to be activated

[josegomezr]

When activating a system from scratch, activating sle-module-containers/15.4/x86_64 raises with:

hydra:~ # suseconnect -r $REGCODE -p sles/15.4/x86_64 -p sle-module-basesystem/15.4/x86_64 -p sle-module-containers/15.4/x86_64
Registering system to SUSE Customer Center

Updating system details on https://scc.suse.com ...

Activating sle-module-containers 15.4 x86_64 ...
Error: Registration server returned 'The product you are attempting to activate (Containers Module 15 SP4 x86_64) requires one of these products to be activated first: Basesystem Module 15 SP4 x86_64' (422)

Which makes sense if I were activating sle-module-containers/15.4/x86_64 alone, but I'm also activating the requirement in the same command.

[djoreilly]

The Ruby version has the same behavior. And the doc says only one product can be specified at a time:
https://github.com/SUSE/connect-ng/blob/e3c41e60892eb6070625d85497f8783f836ef609/suseconnect/connectUsage.txt#L8C7-L9

It's possible to catch this at flag parse time and print a better message.

[digitaltom]

Shall we rename this then to a feature request Support multiple -p parameters?