Implement Detox tests for payment redirection scenarios

Create Detox tests for payment redirection flows commonly used in payment
processing:

### Test Cases:
1. **3DS Authentication Flow**
- Card requires 3D Secure verification
- External browser/webview redirection
- Return to app after authentication

2. **Bank Transfer Redirection**
- Redirect to bank's authentication page
- Handle external app switching
- Verify successful return

3. **Payment Method Redirection**
- External payment provider flows
- Deep link handling on return
- Status verification after redirection

Expected Outcome:
- Robust redirection flow testing
- Handle external app interactions
- Verify deep link returns

Files to Create:
- detox-tests/e2e/redirectionFlow.test.js
- detox-tests/helpers/redirectionHelpers.js

Technical Challenges:
- External app interaction testing
- Deep link simulation
- Async flow handling with timeouts

Acceptance Criteria:
- [ ] Tests handle external app launches
- [ ] Deep link returns are properly tested
- [ ] Timeout scenarios are covered
- [ ] Browser redirection flows work correctly

Start by reviewing the existing Detox setup and running its current end-to-end tests. Then use detox-tests/e2e/redirectionFlow.test.js and detox-tests/helpers/redirectionHelpers.js as the implementation points, covering the listed 3DS, bank-transfer, provider, deep-link, external-app, and timeout scenarios. Done means all acceptance criteria pass.

Written by the indexing model from the issue text.