Fixed compund SPDX expression resolution in detection & clue matches

[OmkarPh]

This fixes the spdx license expression resolution issue discussed in #610

[OmkarPh]

Hey @AyanSinhaMahapatra
Can you share some scans with complex license expressions?
I just want to ensure there aren't any edge cases

[AyanSinhaMahapatra]

LGTM!
Thanks @OmkarPh
The issue was resolved by this.
Here's another scan I used for testing a long license-expression:
test.json.txt

Looks good to me now, should be good. For match-level license-expressions this should be enough, there could be composite license-expression corner cases but no use building a perfect license-expression -> SPDX license expression here in workbench, as that's something that should be (and is presently) handled in SCTK.
Anyway I think we are soon having SPDX license expressions everywhere we have our expressions, so then this will be better as we don't want to do this computation on the workbench side.
Please merge!

[OmkarPh]

Thanks @AyanSinhaMahapatra
Merging !

Looks good to me now, should be good. For match-level license-expressions this should be enough, there could be composite license-expression corner cases but no use building a perfect license-expression -> SPDX license expression here in workbench, as that's something that should be (and is presently) handled in SCTK. Anyway I think we are soon having SPDX license expressions everywhere we have our expressions, so then this will be better as we don't want to do this computation on the workbench side. Please merge!

That's nice 😄
This would still be useful in maintaining backward compatibility