Android: Run Node.js in a ViewModel Coroutine

[jermy-c]

• Moved Node.js into ViewModel
• Redirect C++ std::out and std::out logs to the frontend in Coroutines for debugging errors with SMTP or IMAP
• The C++ Libraries are now loaded in Coroutine also but it is always loaded before running C++ code.
• The Android compileSDK and targetSDK had to be upgraded because androidx.core:core-ktx:1.17.0 would not work
• Build scripts are updated to download libnode and also update the package name and also the directory structure to match the package name
• The Logger Class logs to the frontend if available but always logs to Logcat
• This should replace Android: Run Node.js based on native App lifecycle #900
• A build from this PR: https://github.com/mustang-im/mustang/releases/download/v0.9.9-dev/Mustang-0.9.9-dev.apk

[benbucksch]

I don't know where the kotlin and C++ code comes from?

[benbucksch]

In general, downloading binary blobs is uncool and dangerous. It will get is thrown out of F-Droid (or rejected from), for instance.
It's also against reproducible builds.

[benbucksch]

Idea: Put the libs into an npm release.
Then, get them from node_modules/...
Still a binary module, but at least using the normal package installer dependency system, not just fetching it via https.

[benbucksch]

Does that make any difference which package name the code has?
Can we just leave it as-is?
Does a user see the difference?

I understand that stack traces would be different, but that's rather a disadvantage that an advantage.

[jermy-c]

I think this can be removed we're no longer calling any method from Java.