Collective.contentalerts

------------------

- Test against Plone 4.3, 5.0, 5.1 and (experimental) 5.2.

------------------

- Make collective.contentalerts work with Plone 5
Following adaptions were needed: Remove session_data_manager, use z3c.form instead of
formlib, access text via IRichText object, several changes in tests.
[staeff]

----------------

- Be sure to remove the marker interface only when its needed.
[gforcada]

----------------------
- Update German translation.
[staeff]

----------------
- **Renamed the registry setting**,
now two lists are used: ``forbidden_words`` and ``inadequate_words``.
See the ``README.rst`` for instructions on how to create an upgrade step to migrate them.
[gforcada]

- Updated ``IAlert`` utility to use either both stop words list,
or just one if told so (passed as an argument).
[gforcada]

- Add a ``has_forbidden_words`` method to ``IAlert`` utility.
It allows to check only for forbidden stop words only.
[gforcada]

- Make ``review-objects`` view more generic by allowing a marker interface and review states to be passed.
This allows filtering which elements will be checked for stop words.
[gforcada]

- Triple the content rules so one can decide to monitor for any kind of word,
only forbidden words or only inadequate ones.
[gforcada]

----------------
- Monitor registry setting (stop words) for changes.
If changes are found, verify if reviewed objects have those new stop words.
[gforcada]

- Round of cleanups, refactorings and coverage fixes.
[gforcada]

- Conditionally depend on collective.taskqueue to do mass processing asynchronously.
[gforcada]