Fixes Favorite reordering bug

Favorite reordering had a bug where reordering wasn't saving in the order that the user envisioned.  We were previously only specifying that the moved item be before a destination item.  This commit specifies both the item before and after the moved item.
Comment says "Insert the next sibling before this item."
Method call is `insertNodeBefore(sourceID, siblingID)`.
Method signature is source, destination.
So I read that insert call as "insert sourceId before siblingId", don't I?  Which isn't inserting the next sibling before this item, but is rather inserting this item before the next sibling?

I'm confused?