Summary actually keeping track of full content in javascript

In order to ensure termination of the algorithm even if two items
fall in exactly the same buckets at each and every level, when
there are more buckets in the IBF than there are items to send
over the wire, just send them (the size of the IBF would be larger).

This introduces the full content implementation in javascript, likely
not performing well, and not integrated in summarizers yet.
Summary actually keeping track of full content in java
Unused variable
Bucket selector, digester and summarizer JS documentation
Remove concept of reducing summaries to smaller ones

The concept is too weak as being specific to one summary implementation
and did not make that much sense as it was not defined what a large
summary was (ie: the algorithm would have just failed if the number
of changes exceeded the large summary)
Ability to deserialize fullContent summaries in javascript
Level to size out of umbrella defaults module
Specific arraybuffer serialization module instead of umbrella utility
Ensure identical items are not duplicated in fullcontent
Sort arrays first by lenght before looking at the content
Full content summary to JSON may contain duplicate elements
Deserialize full content summary in java
Document summarizer in index
Rename Summary#plusAsync to Summary#plusIterator
Externalizes iterator utilities
Rationalize generator based summaries into core
Notify of package rationalization in changelog
Summary API reworked in java
Documentation for the existing resolver
Summaries in javascript comply to new API