Adjust zindex droppable logic

[wibed]

adjusted dropping logic on draggable to droppable container, by reversing the order from bottom to top to top to bottom as intuetively assumed

this results on draggables getting dropped into the topmost droppable instead into the lowest.

[100terres]

Hi @wibed 👋

Thank you for your contribution! 👏

I would like to properly understand what we are trying do solve here 🎯

Would it be possible to open an issue detailing what's the current behavoir of rfd and what's you would expect rfd do instead. It would help me a lot review this PR, because I'm missing a bit of context. Also, it would be awesome, if you could provide a link to a CodeSandbox that shows the problem you are facing 🙂

Thank you again!

[wibed]

@100terres

i understand that the repo is in reconstruction and taking up the pace can be daunting.

if you take a peak at the commit, my only doing is reversing the order the droppable is alotted.
atm it does order the droppable to drop to from bottom to top, dropping it into the first it can find.

this results in case of overlapping droppables for the lowest droppable to be used instead of, as mentioned, intuetively
assumed, highest droppable in the order.

this is fixed by reversing the order on the array.

[100terres]

I'll close this PR for now since no issue were opened and no CodeSandbox link were provided.