UI rendering now rejects events with a requestId from a different session instance
The validator that checks arguments for ui.render events (used to draw interactive UI elements) now also rejects an event if its requestId doesn't match the specific instance the UI element was originally drawn in, returning an error about "a requestId other than the instance the element was drawn in". Separately, the logging for ui.close events now logs the event's kind rather than the raw event object.
This prevents a UI event meant for one session or instance from being mistakenly applied to a different one, closing a potential cross-instance mix-up when multiple UI elements or sessions are active.