Issue:
[BUG] Payments list doesn't work with pagination parameters

### Context
- Currently the API accepts payment_id as pagination parameters for e.g starting_after = `pay_Ajabdhakjhah`
- However the underlying code relies on the auto-increment characteristic of databases
- While we do some sort of conversion here our pagination filters are based on `id` whereas the sort is `modified_at`
- This causes the response list to be not actually be paginated but return inconsistent & wrong results

#### Possible Solutions

- Either we can update the pagination filters to use `modified_at` (which can cause inconsistencies with data lists since `modified_at` can be changed)
- We can also try to sort out the list by incremental id


Resolution:
<think>
PR Context:
- Title: fix(router): desc payment list for pagination
- Merged: 2023-07-07T09:11:59Z
- Files changed: 3 files
- Commits: 6 commits

Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->

- [x] Bugfix
- [ ] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD

## Description
Sorted the payment list order in API response for descending based on `created_at` parameter. It allows the database fetches to be asycn and is collected in an hashmap and collected later in a descending order.


### Additional Changes

- [x] This PR modifies the API contract
- 
</think>

To implement this, you'll need to modify:


**Detailed Implementation:**


**Commit 1:** fix(router): desc payment list for pagination (#1556)
Signed-off-by: NavinShrinivas <karupal2002@gma
Files to modify:


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

**crates/router/src/types/storage/payment_intent.rs**
  Modify existing code