CMS-9898: rollback changes from release preparation of hippo-plugin-poll-2.2.0-rc-1

CMS-9899: copy for branch hippo-plugin-poll-2.2.x

HIPPLUG-1083: added comments to content(prop)deletes to remove them in next major version

HIPPLUG-1083: merged the branch poll-2.x-cleanup into trunk

HIPPLUG-1200 rollback changes from release preparation of poll-2.1.0-translations-1

CMS7-9483: prepare for next development iteration

HIPPLUG-1162: prepare release hippo-plugin-poll-2.0.0

HIPPLUG-1139: prepare for next development iteration

HIPPLUG-1079: prepare for next development iteration

HIPPLUG-1076 backwards compatible change in poll logic that instead of having to point a folder that contains one or more polls and the first poll is used, you can now just explicitly select a poll document in the component properties window in channel mngr. That is I think much easier to understand. I did leave the existing PollComponent and PollComponentInfo interface untouched to make sure already existing polls keep working. I extended both to now have the PollDocumentComponent for which you can pick a poll document instead of a folder. I reload the catalog item so for customers upgrading, the old already used polls keep working and for newly added polls to a page in the channel manager, they have to select a poll document instead of a folder

HIPPLUG-1065: prepare release hippo-plugin-poll-1.09.00-alpha-1

HIPPLUG-970: fix maven coordinates of standard Hippo Plugin Poll

HIPPLUG-970: initial import of the poll standard plugin for CMS 7.10, cloned (unmodified) from the Forge poll plugin