compositor: Fix opaque regions
Commit 0e4f097d broke opaque regions, and since then weston will waste time rendering occluded areas.
I think this is because we're taking the intersection of the opaque and scissor regions even when the scissor region isn't enabled.
An easy test is to turn on triangle fan debugging with the gl renderer, then run weston-simple-damage and move another opaque application such as weston-terminal over it.
Signed-off-by: Derek Foreman derek.foreman@collabora.com