JUCE issue: cannot replace MainLauncher to aap-core PluginListActivity

[atsushieno]

Currently, aap-juce plugin ports launch JuceActivity, which is the main entrypoint of the app. But they are in general useless because they are designed to run as a plugin UI (we are seeing Standalone build of the app). It is not what we intend to show.

What we should do instead is to show the "plugin settings and playground UI" aka. PluginListActivity in androidaudioplugin-ui-compose. Then it can present "Show UI" command to switch to it (or show overlay Window if possible).

Bonus if it can control the plugin instance in use (but needs connection management).

[atsushieno]

It is actually quite a bit tricky as JUCE behavior is quite bad and hijacks MainLauncher specification in AndroidManifest.xml and behaves as if JuceActivity were the main launcher.

[atsushieno]

They indeed hijacks what I have specified! https://github.com/juce-framework/JUCE/blob/d054f0d14dcac387aebda44ce5d792b5e7a625b3/modules/juce_core/native/juce_Threads_android.cpp#L218