Fixed ChooserPresenter moving and filtering items

[JanBliznicenko]

Fixes #1340, pharo-project/pharo#13907 and #1493.

• In order to fix losing items, instead of remembering original sourceItems then trying to re-calculate from these after every move, use actual items in both lists
• Merged duplicite parts of code for moving items
• In order to fix filtering after moves: If the filter would result in empty list, clear the filter. if the filter would result in at least some shown items, reapply the filter. Always match filter field text with actually applied filter.
• Moved sorting responsibility to ListPresenters (use SpAbstractListPresenter sortingBlock) instead of Chooser replacing lists items after sorting "manually" (the chooser now only provides sortingBlock during initialization)

[estebanlm]

let's wait for what Cyril has to say, otherwise it looks ok, I will approve preemptively :P

[estebanlm]

convention is actually put tag before package (because then the template will work correctly, otherwise it doesn't). I do not think this is an issue in monticello, however... maybe @jecisc knows ?

[jecisc]

I added the tag after the package in the Tonel format because I did not really think about the order in other places :(

So this is not related to this PR