Issue:
chore(analytics): create a seperate flow for a force sync

Currently we use PaymentRetrieve for GET /payment/:id call, for force_sync use cases we should have a separate flow since the underlying execution differs significantly...

Resolution:
<think>
PR Context:
- Title: feat(analytics): add force retrieve call for force retrieve calls
- Merged: 2024-02-28T13:54:43Z
- Files changed: 7 files
- Commits: 12 commits

Implementation approach:
Currently we use PaymentRetrieve for GET /payment/:id call, for force_sync use cases we should have a separate flow since the underlying execution differs significantly...
Refs: #3562

## Type of Change
<!-- Put an `x` in the boxes that apply -->

- [ ] Bugfix
- [x] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD

## Description
<!-- Describe your changes in detail -->
Currently we don't show payment retrieve call logs in t
</think>

To implement this, you'll need to modify:


**Detailed Implementation:**


**Commit 1:** feat(analytics): add force retrieve call for force retrieve calls (#3565)
Co-authored-by: harsh-shar
Files to modify:


**crates/router/src/compatibility/stripe/payment_intents.rs**
  Modify existing code

**crates/router/src/compatibility/stripe/refunds.rs**
  Modify existing code

**crates/router/src/compatibility/stripe/setup_intents.rs**
  Modify existing code

**crates/router/src/routes/lock_utils.rs**
  Modify existing code

**crates/router/src/routes/payments.rs**
  Modify existing code

**crates/router/src/routes/refunds.rs**
  Modify existing code

**crates/router_env/src/logger/types.rs**
  Modify existing code