client: clientConfigure: simplify catching border_width

Along the clientConfigure() call path, we're catching up potential changes
in window's border_width attribute into internal state, used on reparenting.
Potential sources are intercepted configure requests and netwm hints.
Deep down the road (clientConfigureWindows()) the corresponding mask flag
is cleared, so this change isn't passed to the Xserver - we just record it.

In order to improve code clarity, making a clear border between recording
changes and applying our current state, moving this further up the call
chain, near to where the data arrives, into clientMoveResizeWindow().

With more subsequent patches, we'll reach a point where clientConfigure()
doesn't touch any internal state anymore (except applying constraints),
but just writing out what we already have.

Signed-off-by: Enrico Weigelt, metux IT consult <info@metux.net>
2 jobs for !90 with submit/clientConfigure_border_width in 2 minutes and 41 seconds (queued for 4 seconds)
latest merge request