are_multiple_claim_values_allowed controls all claims in a scope

[mrvanes]

If I set are_multiple_claim_values_allowed to true in a custom scope eduperson, which I need for eduperson_affiliation, eduperson_principal_name also becomes a list even if it contains only one value (and is defined as single-valued).
Maybe the are_multiple_claim_values_allowed setting should live at the claim definition level instead of scope?

Or: Always send single valued claims as string and expand to list if are_multiple_claim_values_allowed is set to true at the scope level, this would be the least intrusive refactor. But the downside is that this behaviour would be unpredictable for the RP.