Issue:
refactor(RouterData): reorder fields in `RouterData`

## Type of Change
<!-- Put an `x` in the boxes that apply -->

- [ ] Bugfix
- [ ] New feature
- [x] Enhancement
- [ ] Refactoring
- [ ] Dependency updates

## Description
This change targets on changing the orientation of the fields in RouterData the change is as follows
```diff
struct RouterData<Flow, Request, Response> {
-     response: Option<Response>,
-     error_response: Option<ErrorResponse>,
+     response: Result<Response, ErrorResponse>,
}

```
<!-- Describe your changes in detail -->


### Additional Changes

- [ ] This PR modifies the database schema
- [ ] This PR modifies application configuration/environment variables

<!-- 
Provide links to the files with corresponding changes.

Following are the paths where you can find config files:
1. `config`
2. `crates/router/src/configs`
3. `loadtest/config`
-->


## Motivation and Context
This change was intended in earlier revisions on the project but due to the rapid growth of the codebase in the connector side, this change needed to be retargetes
<!--
Why is this change required? What problem does it solve?
If it fixes an open issue, please link to the issue here.

If you don't have an issue, we'd recommend starting with one first so the PR
can focus on the implementation (unless its an obvious bug or documentation fix
that will have little conversation).
-->


## How did you test it?
⚠️ Under testing by @Gnanasundari24
<!--
Did you write an integration/unit/API test to verify the code changes?
Or did you test this change manually (provide relevant screenshots)?
-->


## Checklist
<!-- Put an `x` in the boxes that apply -->

- [x] I formatted the code `cargo +nightly fmt`
- [x] I addressed lints thrown by `cargo clippy`
- [x] I reviewed submitted code
- [ ] I added unit tests for my changes where possible
- [ ] I added a [CHANGELOG](/CHANGELOG.md) entry if applicable


Resolution:
<think>
PR Context:
- Title: fix(payment_update): fix the fsm after passing pm_data in update
- Merged: 2022-11-29T17:56:36Z
- Files changed: 1 files
- Commits: 1 commits

Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->

- [x] Bugfix
- [ ] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates

## Description
The addition of payment_method_data in `PaymentData` affected condition for checking payment method in `update_tracker`  where the check for available payment method is done.
<!-- Describe your changes in detail -->


### Additional Changes

- [ ] This PR modifies the database schema
- [ ] This PR modifies appl
</think>

To implement this, you'll need to modify:


**Detailed Implementation:**


**Commit 1:** fix(payment_update): fix the fsm after passing pm_data in update (#38)
Files to modify:


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