Over the texture budget, a render target the GPU drew is written back into the game's memory before it is evicted
(issue 386). The write covers all of its storage and marks those pages written. OoT draws its HUD's labels (the d-pad
icon, the item count, the key prompt) inside the storage of a 1920x1080 target it has stopped using. When that target
was evicted about 600 frames later, the finalized labels counted as written by the CPU and were uploaded from memory
that never held their texels: they showed as noise until the pause menu redrew them. Seen at a 6,144 MB VRAM
allowance in Hyrule Field; RX_VK_EVICT_NO_FLUSH=1 hid it.

The eviction now skips the write-back of a texture when another image was drawn into its storage after its own last
drawing (evict_reason::write_back_stale, with drawn_others, which the drawn write-back already uses). Such a texture
goes with no copy of its texels, as the log's "no copy kept" count says. A drawing in the same frame keeps the
write-back.

Assisted-by: Claude Fable 5.2
Co-Authored-By: Claude Fable 5.2 <[email protected]>

@@ -4680,0 +4686,4 @@
+        for (const Evict& e : evict)
+            if (e.flush) ts.push_back(e.tex);
+        if (!ts.empty()) {
+            const std::vector<uint64_t> other = drawn_others(ts);

@@ -4680,0 +4689,4 @@
+            const std::vector<uint64_t> other = drawn_others(ts);
+            size_t i = 0;
+            for (Evict& e : evict)
+                if (e.flush) e.flush = !evict_reason::write_back_stale(e.tex->last_written, other[i++]);