[dasc] Arrays support min/max

As an author, I would like to know if I am under or over an array's min / max values.

## Criteria of acceptance
1. Uses existing validation tools to flag if over or under.
2. Does not _prevent_ or _force_ a min / max as the author should be able to over / under shoot to better organize WIP.

## Additional context
At first I thought we would want to enforce this, but I think its better to let an author work with the validation signals to get into compliance. If you think about an author that has 4 items, needs to shuffle data around, but cannot add a 5th until they remove another. The same is somewhat true of mins. I think we would end up getting a lot of empty items rather than correct data.

Start by locating the existing validation path for dasc arrays and the tests covering current validation signals. Trace how array minimum and maximum values are represented and reported. Done means over- and under-limit arrays produce validation feedback without blocking authors from creating or editing those arrays.

Written by the indexing model from the issue text.