Correctly consider cardinality based on the directives

[laeubi]

Currently the BundlesAction uses either 0 or 1 as the cardinality but actually a requirement can be a multi-cardinality as well.

This adds new dedicated methods to not duplicate the computation and a testcase that ensures all combination are covered and correctly translated.

[laeubi]

cardinality:=multiple is not very common but we still should map this correctly, @tjwatson @merks should this go into RC1 or should we wait for the next release?

[merks]

Can you summarize the impact. I believe it just means that if there is a cardinality:=multiple the requirement will have max=MAX_INT. Otherwise nothing is changed, correct?

[laeubi]

Yes currently it is either 0..1 or 1..1, but it is also possible that it is 0...n and 1...n if you look at the manifest I used for the testcase it should be more clear.

[github-actions]

Test Results

    9 files  ±0      9 suites  ±0   29m 41s ⏱️ -36s
2 197 tests +1  2 193 ✅ +1   4 💤 ±0  0 ❌ ±0 
6 681 runs  +3  6 670 ✅ +3  11 💤 ±0  0 ❌ ±0 

Results for commit 2b2c924. ± Comparison against base commit 4426f86.

♻️ This comment has been updated with latest results.

[laeubi]

As no one raised concerns I'll merge this as soon as build completes.