[req] bound_claims notation allowing for the "and"ing of claims from a list

If a JWT has the following claim:
```json
{
"foo": ["c", "d"]
}
```
it will match on a `bound_claims` value of
```json
{
"foo": ["a", "b", "c"]
}
```
since that rule indicates that the `bound_claims` match on a list "foo" containing either "a" _or_ "b" _or_ "c".

I would like to see a feature in which a `bound_claims` map can be written to specify that the list "foo" must contain more than one specific value, e.g. "c" _and_ "d".

Start by tracing how bound_claims values for JWT list claims are parsed and matched. Define and document a notation that requires both "c" and "d" in the foo claim, then add coverage showing that a token containing both values matches while tokens containing only one do not.

Written by the indexing model from the issue text.