[hckrman101]

Fixes most of the remaining one-frame flashes on Linux (#371): haze and sun shafts appearing or vanishing for one frame, with the environment brighter or darker while the HUD and characters stay the same.

OoT's presentation queues submit a frame's work before two things it waits for are ready: the scene work (through event waits) and the CPU's writes for that frame (the CPU signals an event when it has finished). Two paths replayed that work against the previous frame's data.

Forced waits. Every NVN queue shared one fence timeline, and it only advanced as far as the oldest submission stopped at a wait. Three things waited on that timeline and pushed the presentation queues' stopped work past its waits:

• the exposure readback's catch-up (the write-back wait from OoT exposure flashes: CPU reads of GPU results wait for the work that writes them #296);
• the texture readback's catch-up;
• waits on main-queue fences.

Fences are now per queue: nvnQueueFenceSync takes the queue's own last submission. They are waited on through a second timeline that numbers the recordings. The readbacks no longer force anything through. RX_VK_PER_QUEUE_FENCES=0 restores the old behaviour.

Stale captures. The memory capture was taken at submit time, so it held the previous frame's data. Now a submission stopped at a wait for a CPU-signalled event takes a fresh capture of the CPU's writes when it resumes, because the console's GPU reads memory after its wait. RX_VK_RESUME_CAPTURE=0 turns this off.

Measured on Linux with an RTX 3090: Kokiri Forest save, standing still, 60 s frame log on a 75 Hz monitor, one-frame events counted with scripts/framelog.py.

Build	Events	Frames	fps
Before (ba594da)	26	2900	~48
After	10	3586	~60

The frame rate goes up because the main thread no longer blocks on the other queues' stopped work.

Diagnosis:

• 144 of 150 events followed a forced drain.
• Once forcing was removed, 87 of 92 events followed a stop at the CPU event's wait.

Known gaps:

• The 10 remaining events aren't explained yet.
• A fence taken on a queue that is itself stopped still falls back to the old forced path.

The branch is rebased onto current main (after #416). The test now checks take_capture(), which both capture paths share, for cap_view_bump(). The numbers above were measured on ba594da.