feat(mobile): implement claim sharing workflow for senders

[memplethee-lab]

• Add share sheet integration using expo-sharing for native mobile sharing
• Add copy link functionality with visual feedback using expo-clipboard
• Add QR code generation using react-native-qrcode-svg
• Create ShareSheet component with copy, share, and QR code options
• Update SenderFlow success screen with share button
• Install dependencies: expo-sharing, react-native-qrcode-svg, react-native-svg

Closes #56
: Build claim sharing workflow for senders

• Share sheet works on Android/iOS
• Links copy successfully to clipboard
• QR codes render correctly for claim links

Executive Summary

Linked Issues & References

• Issue: Resolves #
• Related PRs:

Type of Change

Category

• New Feature (Non-breaking change adding functionality)
• Bug Fix (Non-breaking change fixing an issue)
• Performance Optimization (Code change to improve efficiency)
• Refactoring (Code structure change without external API modification)
• Security Patch (Fixing a vulnerability or security concern)
• Documentation (Updates to README, Wiki, or inline docs)
• Infrastructure (CI/CD, build scripts, Docker)

Domain

• Smart Contracts (Rust/Soroban)
• SDK/Backend (NestJS/TypeScript)
• Frontend/UI

Technical Implementation Details

Breaking Changes

• No - Backward compatibility is maintained.
• Yes - This change requires consumers of the SDK/Contract to update their code.

Verification & Testing Strategy

Automated Tests

• Unit Tests: Added/Updated new unit tests.
• Integration Tests: Verified interaction between modules.
• Linting: Code follows the project's style guide.

Manual Verification

1. Environment:

• Target Environment:

2. Reproduction Steps:

3. Proof of Execution:

Quality Assurance Checklist

• I have performed a self-review of my own code.
• I have commented on my code, particularly in hard-to-understand areas.
• I have updated the documentation to reflect these changes.
• My changes do not generate new warnings or errors.
• I have verified that new dependencies are necessary and secure.
• (If Smart Contract) I have verified gas usage and storage footprints are optimized.

---

By submitting this Pull Request, I acknowledge that I have adhered to the Bridgelet contribution guidelines.

[drips-wave]

@memplethee-lab Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits