Remove Wayland::Client usage in wl->xwl drags
For clipboard usage we made wayland to xwayland avoid going through an internal wayland connection.
For drag and drop we were left with a mixture. This led to an awkward situation where we could process endDrag before we received the drop event. By handling the data source directly we avoid this situation.
Testing done:
- dragging files onto chrome now gets accepted as new tabs
- we still seem to have an issue with drag offers not always being accepted by the client, but this appears to be an existing bug.
The helper functions appear duplicated because we have both client enums used in xwl->wayland drags.
Edited by David Edmundson