Initial stab at limiting term size during logging
Avoid binary:part/3, since it isn't available in R13
Start testing this properly
Skip tests in a more operator friendly way
Reduce the size of the test inputs

Don't hit 110% CPU (thanks for that PropEr) and get usable failures sooner.
Avoid crashing as we approach Len == 0, improve test output
Tweak list handling
Tweak a bit more - attempt to handle bitstrings properly
Rename module and functions to be shorter and more generic. Remove quickcheck tests. Wire into the non-sasl error_handler, but don't wire into handle_info and handle_call functions since those should not be logs.
Don't let the truncate module have any opinion on how much to truncate.
Remove obsolete TODOs, fix a rather substantial bug.
Something of a rewrite:

* Allow choice of how much size to "eat" each time we descend
* Fix at least one more recurse-indefinitely bug
* Try to reduce the amount of copying we do, and use more efficient techniques
* Add some tests
Several more changes:

* Remove the special tuple handling, it was trying to not reduce depth as we went "along" a tuple, but that goes badly in real world tests with gb_trees and gb_sets. In fact we just want to treat a tuple exactly like a list.
* Simplify and correctify a bit by only having one termination condition for depth.
* Add some more tests, and correct some existing ones.
cosmetic
Those aren't log events
More robustness in the shape of unusual events.
tiny tidying
Fix bitstrings, export term/3.
Have a completely separate counter for content size vs structural size.
Tweak values based on some testing.