Consider a requirement's filter and max when computing dependencies

[merks]

#3197

[laeubi]

@merks thanks for looking into this, sadly this now fails to discover dependencies from SWT>Fragement (at least I suspect that's what the error in "Individual Bundles Build" seem to cause). so I think one can not completely ignore any requirement that has a filter.

[github-actions]

Test Results

384 files  +2  384 suites  +2   2h 17m 37s ⏱️ - 32m 34s
377 tests +1  365 ✔️  - 5    6 💤 ±0  1 ❌ +1  5 🔥 +5 
754 runs  +2  731 ✔️  - 8  13 💤 ±0  1 ❌ +1  9 🔥 +9 

For more details on these failures and errors, see this check.

Results for commit 208b1c6. ± Comparison against base commit b193066.

[laeubi]

@merks thanks for the testcase this was included here:

• Pass the profile properties so they can be considered in the resolve #3204

and should support full profile properties filtering.

[merks]

Changes this this have superseded this attempt, and the following test case is much simpler:

#3227