fix(mobile): stop shared content errors in Personal Team builds - #4943

💭 I need to check whether this new module follows the codebase conventions—it looks like a closure-based helper rather than an Effect service, so I should verify if that's intentional or if it's hiding state in a way that violates the pattern. Let me examine the IncomingShareProvider and related files to understand how the sharing feature is structured. This PR doesn't involve any Effect service creation, movement, refactoring, or consumption—it's just plain TypeScript and Promises. The test file uses "@effect/vitest" but that's just repo convention. So there are no findings to report, though I'm noticing a tension between the instruction to respond with "All clear" and the requirement for JSON schema formatting.