If EntityTreeModel::modelIndexForCollection() doesn't find the
collection we're dropping, then insert it first (via the base class
dropMimeData) and then look for it again, to handle it as a move.
I hope this doesn't affect other EOPM users than the favorites model;
but when reordering a full ETM surely the dropped folder is somewhere in the
ETM.