initJvmEventLoop

Installs remidy's event loop.

On macOS the main thread is the AppKit main thread, not the AWT event queue. Everything remidy marshals to "the main thread" has to land there: clap_plugin_factory.create_plugin and clap_entry.init are main-thread calls by the CLAP spec, and a JUCE-based plug-in binds its MessageManager to whichever thread runs them. Bind that to the AWT event queue and the plug-in's message thread is a thread with no CFRunLoop — one that AWT also retires when it goes idle — so the MessageManagerLock the same plug-in takes in guiCreate is never granted and creating its UI hangs for good. Instancing on the AppKit thread is also what uapmd-app does, since there the main thread is the only thread.

Elsewhere the AWT event queue is the UI thread and is used directly.