can i call plugin.loadimplementation for a plugin in another bundle?

AI generated answer (using internal Slack threads):

Based on the conversations provided, it seems that the question 'can i call plugin.loadimplementation for a plugin in another bundle?' was not directly addressed. However, there are some relevant points that can be inferred. From the first conversation, it is suggested that a component should be available in Bundle inclusion once it is set to public. This implies that components from one bundle can be accessed by another, given the right settings. The second conversation discusses the possibility of using components from one bundle in another. The responses suggest that this is possible, but caution is advised, especially if the original bundle is uninstalled. The third conversation discusses executing a bundle install script outside of the actual bundle install/update/delete. The responses suggest that this is not possible without writing another script, but recommend extracting the logic into a custom module and invoking the method from there. In conclusion, while it is not explicitly stated, it seems likely that you can call

plugin.loadimplementation

for a plugin in another bundle, provided the plugin is set to public and the necessary precautions are taken. However, this is an inference and may not be entirely accurate. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******