Overlays: message queue exceeds VK_OVERLAY_MAX_DRAW_CALLS

[Megamouse]

The emulator crashes when you push an unreasonable heap of messages into the overlay message queue.
This is probably happening because we immediately try to render them on screen, even when they are offscreen anyway.

So my suggestion is to keep them queued in memory until they can actually be displayed and also restrict the visible items to a fixed number.

We can also just drop duplicate messages that are still waiting, or simply refresh a visible message somehow.

[elad335]

All mesaages can be ref-counted and disabled manually now, the logic can be applied externally.

[kd-11]

The logic should be handled by the overlay to display a reasonable number of messages on screen. The error thrown is just the backend refusing to issue thousands of draw calls to draw a simple UI as it is a sign that something has gone wrong.
I recommend a buffered queue with only 3 visible messages at a time.