Optimized handling of scheduled collections for update and removal.

[watari]

Q	A
Type	feature/improvement
BC Break	no
Fixed issues

Summary

Was updated handling of scheduled collections for update and delete. Added to CollectionPersister methods deleteAll and updateAll. In added methods query "per-collection" replaced on query "per-parent" where it is was possible.

I added tests only for deleteAll method of CollectionPersister. Functional tests is covers updateAll method. Should I also add separate functional tests for deleteAll method?

[jmikola]

@watari: This looks like it incorporates all of #1880 and adds updateAll. We would like to target any new functionality to the master branch, and then manually backport it to 1.3 after the fact. This isn't a candidate for 1.2 because it's introducing new public API to CollectionPersister.

Can you please revise/rebase this PR so it targets the master branch? And then consider closing #1880 if it is indeed redundant.

[watari]

@jmikola, there is discussion about this PR in Gitter.
In short, I implemented it in 1.2.x branch since I have project that use this version of ODM and can perform tests in it. So it is faster for me to make changes. Also my project will use my fork with branch 1.x or your 1.3 (when it will be released) before 2.x will become stable.
When @alcaeus take a look at this PR and confirm that it can be used also for 2.x I will update #1880 to reflect same changes (DocumentPersister and CollectionPersister is same in both branches).

I can revise/rebase PR for 1.3.x branch. this PR and #1880 was intended provide same updates for different branches.

[watari]

Close this PR. Proposed changes will be moved to PR #1882 (for master).