Revert "window-wayland: Make sure to save where the position for server-initiated resizes"

This is wrong for client-initiated resizes now.

This reverts commit e6b0525c709def2e9de792bb09c6c42391777468.
Revert "window-wayland: Don't enter the only-moving path for Wayland
resizes"

We're going to use the old code structure now.

This reverts commit 23ae11043f298fc8489c5f1436ff613b39c61072.
window-wayland: Make sure to save where the position for server-initiated resizes

For the server-initiated resize case, like unmaximize or some forms
of tiling, we dropped the x/y of the server-assigned rectangle on the
floor, which meant the surface didn't move to where it needed to be in
that case. Now, save it internally, and combine it with the dx/dy passed
in during attaches to figure out where we actually need to be.

Make sure to only use it for when we send out a configure notify. We
should use the passed in rectangle for other scenarios, like a
client-initiated resize.

This fixes incorrect surface placement after unmaximization.