Should throw MaxElementsExceededException when multi-valued option max arity exceeded

[remkop]

Current (0.9.8) behavior is wrong: when processing split values, values exceeding max arity are pushed back onto the stack and are likely interpreted as positional parameters.

Instead, a MaxElementsExceededException should be thrown when the arity of a List or Map option has an upper bound, and the user specifies more values than the max.