add size limited pymaps and pylists

[boulter]

User-provided templates should not be allowed to use unlimited resources. This is a failsafe that adds a limit the maximum size of lists and maps. The default is no (practical) limit.

This is similar to #137

[mattcoley]

Throwing the OutputTooBigException in the LengthLimitingStringBuilder has been a bit of a mess trying to handle that runtime exception in multiple places. Would it make better sense to truncate the collection to keep it under the limit and add a warning? This would protect against the situation where data being pulled in gets continually larger until it trips the limit which could break templates rather than just truncate them.

[boulter]

This throws an IndexOutOfRangeException which extends InterpretException, so may be already handled. OutputTooBigException extends RuntimeException directly. You could argue that IndexOutOfRangeException is not quite right and maybe I could add another exception which also extends InterpretException.

[jasmith-hs]

I like this idea. If it's wrapped in an ELException, it would be handled here by adding a warning-level template error

[jasmith-hs]

Integer overflow might be a concern. It should be safer to do size() >= maxSize - elements.size()

[boulter]

I think we will run out of memory long before this if a collection has 2B items in it!

[boulter]

@mattcoley I decided to create a new CollectionTooBigException because IndexOutOfRangeException was not appropriate and this is a pretty severe error. I don't want to just ignore it and continue because it could end up creating thousands of error messages. These limits are really high, so I don't think this will come up very often, but it should save the renderer when it does.

[jasmith-hs]

What if it's a warning when it's at like 90% capacity to help prevent the situation that Matt described

[boulter]

What if it's a warning when it's at like 90% capacity to help prevent the situation that Matt described

Done. Check it out.

[jasmith-hs]

Nice