fix: disabled monitor no tagsset

hotfix: do not lose focus on tags moving between monitors

fix: attachclients in applyrules

fix: attach client to different monitor for tagrules

fix: singletagset unexpectedly changed selmon

When viewing tag that was previously on another monitor,
and the current monitor was empty, this lead to selmon
being changed, since focusclient(focustop(origm), 1) cannot
change the monitor in this scenario

fix: correct behavior with other patches that change VISIBLEON

This fixes problems with patches like istticky,
where the sticky window would be visible on every monitor.
It's not. It should be visible only on its monitor.
SVIBISLBEON should always be adapted with those patches.
It's used just for singletagset when looking where a window
should be visible

fix: attach clients to reenabled monitor

fix: do not segfault on selmon NULL

Fix clients with NULL monitor being VISIBLEON

Fix getunusedtag, attachclients

If client is on multiple monitors, it should
be hidden, as the client is visible just on one of
the monitors, and on the other there is empty space instead

Unused tags are only the tags that are not on any
of the monitors.

singletagset

dwl-patches overhaul - doc changes

Update wmenu-run name

switch to wmenu

bemenu is very bloated, turning itself into a library, which makes it
7489 SLOC.

wmenu on the other hand, looks suckless by default, and is only 2000
SLOC, which i also find alot nicer to use, since bemenu does nothing
to replicate the original dmenu feel.

put wlr_layer_shell top layer below fullscreen

fixes wlr_layer_shell top clients showing over fullscreen clients

do not set withdrawn state for xwayland clients

Closes: https://codeberg.org/dwl/dwl/issues/573

properly resize on configurex11

Fix rule examples; minimize newbie surprises

Make example rules be actual EXAMPLES.
Now newcomers should not have to ask, "When I start firefox, nothing
happens. What is going on?"

Also clarified a minor typo and a consistency in spacing.

fix virtual pointers

When motionabsolute() is called from warpd, event->time_msec is 0, so
motionnotify() doesn't call wlr_cursor_move(). Fix this by explicitly
warping the cursor in this case, like it was done before implementing
pointer constraints.

I don't know if this is a bug in warpd or time_msec is always 0 with
virtual pointers, since the only other software that uses the virtual
pointer protocol I know of is wl-kbptr, and I can't get that to work
with dwl at all.

Support pointer constraints and relative pointer protocols

Fixes: https://codeberg.org/dwl/dwl/issues/489
FIxes: https://codeberg.org/dwl/dwl/issues/317