User interface to allow opening in another app? (Open-with functionality)

SolidOS using the data browser hack is in a privileged position where its registered panes are the default view when navigating to a resource.
Even if dynamic panes become possible (https://github.com/SolidOS/pane-registry/issues/28), this provides an inward-focused experience rather than encouraging interaction with a broader ecosystem of specialised apps.

It turns out that in the context of SAI and the principle of least privilege, there is also the opportunity for SolidOS to act as a bridge to enable follow your nose between apps.
https://github.com/solid/data-interoperability-panel/issues/325

I'm opening this issue to discuss what user interface SolidOS should provide to help the user open a resource in another app.

As test cases, one could consider offering to open:

• Dokieli as a standalone app rather than as a pane
• recipes in Umai
• Resources or containers in Solid File Manager, Solid Content Manager, Penny or PodOS
• ...

Start by reviewing the issue discussion and the linked pane-registry and data-interoperability-panel issues to understand the proposed cross-app behavior. Use the listed test cases—Dokieli, Umai, Solid File Manager, Solid Content Manager, Penny, and PodOS—to define the required user interface and its acceptance criteria. No implementation files or tests are named in the issue.