Reduce OSD and notification layer surface area

[nicknack5050]

Volume/status OSDs and notifications currently allocate transparent layer surfaces across the output even though their visible content occupies a small area. On a 4K desktop this substantially increases the surface area presented to the compositor during overlay activity.

This change sizes the OSD surface to its measured card, keeps it centered with the same bottom margin, and retains its empty input region. Notification surfaces become narrow right-hand strips while preserving full height, popup positioning, and the column input mask. Compositor animations are disabled for these surfaces; the OSD's progress animation remains intact.

Validation: focused OSD and notification suites pass, including surface-sizing and click-through assertions. The equivalent local compact OSD was inspected in the running desktop and through hyprctl layers: a volume card occupied 256×60 logical pixels on a 2400×1350 logical output. This establishes the surface reduction, not a quantified GPU or audio improvement. Private desktop captures are not attached.

Full ./test/all: CLI suite passed; 228 of 236 shell test files passed. Failures: bar-icon-geometry, config, launch-about, locate, runtime-smoke, snapper, unowned-system-paths, and update-lock. Bar geometry and About failures were reproduced on clean upstream 31bd80d; several checks require a sibling omarchy-pkgs checkout absent here. The other failures are reported without attributing a cause; the two branch suites were run concurrently in a live desktop environment. The same eight failures occurred on the favicon-only branch, which does not modify overlay code. OSD and notification tests passed.

Draft pending clean before/after visual captures and broader layout verification (notification stacking, alternate bar positions, and scale factors). This does not change audio buffering or NVIDIA driver settings and does not claim to resolve all audio underruns.