Mobile: Fix plugins aren't visible after switching to a new profile

[personalizedrefrigerator]

Summary

Fixes an issue where plugins weren't visible in settings after switching to a new profile, despite being installed.

Note: Review #10348 first.

Notes

Important

This pull request builds on the changes made in #10348 (which has not yet been merged). This is done to avoid a regression that would cause the background webview to load even when no plugins are installed/plugin support has not been enabled.

Previously, the background plugin runner WebView was loaded only if settings existed for at least one plugin:

joplin/packages/app-mobile/plugins/PluginRunner/PluginRunnerWebView.tsx

Line 83 in 443e04b

const hasPlugins = Object.values(pluginSettings).length > 0;

This may not be the case if the user switches profiles, in which case this setting would be empty. However, plugins are still installed and installing one additional plugin would cause all plugins to be loaded.

The PluginStates setting screen previously also relied on pluginSettings. As a result, plugins installed in a different profile could run in the background with no UI in the plugin settings screen. This has been fixed by making PluginStates get information about the loaded plugins directly from PluginService rather than from settings and Redux state.

Testing

This pull request has an automated test. The test checks that installing and uninstalling plugins updates the plugin settings screen.

To test this manually,

1. Open a profile with existing plugins.
2. Install a new plugin (tested with the CodeMirror 6 Snippets plugin).
3. Switch to a new profile.
4. Enable plugin support in settings.
5. Verify that all plugins from the previous profile are visible in settings.
6. Delete the plugin installed in step 2, verify that it is removed from the list in settings.

This has been tested successfully tested on Android 13.

[laurent22]

#10348 is merged now but as a result there are some conflicts