Bug: [BUG] PSync does not change the payment status for NMI connector



### Bug Description

It bugs out when you do a payment and make a PSync call. For context, NMI requires you to do a PSync to update the payment status every time you make a payment. Now that, with PSync flow not updating the payment status after doing a transaction, the `payment_status` remains in `Processing` even after the payment is succeeded (verified through the dashboard).

### Expected Behavior

After the PSync is called, the actual payment status has to be updated. Say, if the payment is completed and successful, the payment status should not be in `processing` state but rather in `succeeded` state. 

### Actual Behavior

The payment status never gets updated.

### Steps To Reproduce

Provide an unambiguous set of steps to reproduce this bug. Include code or configuration to reproduce, if relevant.
1. Make a payment through NMI, payment status will be `Processing`
2. Do a PSync call, with `force_sync` set to `true`, it will still be in `Processing` state instead of changing to `Succeeded`.

### Context For The Bug

<img width="1292" alt="image" src="https://github.com/juspay/hyperswitch/assets/69745008/bc4e6997-a742-40ff-9017-bbc8b61f86a2">


### Environment

Are you using hyperswitch hosted version? Yes
Integ x-request-id: `62f03b59-0521-4fce-9364-fd3531262112`


### Have you spent some time to check if this bug has been raised before?

- [X] I checked and didn't find similar issue

### Have you read the Contributing Guidelines?

- [X] I have read the [Contributing Guidelines](https://github.com/juspay/hyperswitch/blob/main/docs/CONTRIBUTING.md)

### Are you willing to submit a PR?

Yes I am willing to submit a PR!
diff --git a/crates/router/src/connector/nmi/transformers.rs b/crates/router/src/connector/nmi/transformers.rs
index eb09497cede..a99c1c9f4ba 100644
--- a/crates/router/src/connector/nmi/transformers.rs
+++ b/crates/router/src/connector/nmi/transformers.rs
@@ -510,8 +510,7 @@ impl From<NmiStatus> for enums::AttemptStatus {
             NmiStatus::Abandoned => Self::AuthenticationFailed,
             NmiStatus::Cancelled => Self::Voided,
             NmiStatus::Pending => Self::Authorized,
-            NmiStatus::Pendingsettlement => Self::Pending,
-            NmiStatus::Complete => Self::Charged,
+            NmiStatus::Pendingsettlement | NmiStatus::Complete => Self::Charged,
             NmiStatus::InProgress => Self::AuthenticationPending,
             NmiStatus::Failed | NmiStatus::Unknown => Self::Failure,
         }
@@ -633,10 +632,8 @@ impl From<NmiStatus> for enums::RefundStatus {
             | NmiStatus::Cancelled
             | NmiStatus::Failed
             | NmiStatus::Unknown => Self::Failure,
-            NmiStatus::Pendingsettlement | NmiStatus::Pending | NmiStatus::InProgress => {
-                Self::Pending
-            }
-            NmiStatus::Complete => Self::Success,
+            NmiStatus::Pending | NmiStatus::InProgress => Self::Pending,
+            NmiStatus::Pendingsettlement | NmiStatus::Complete => Self::Success,
         }
     }
 }
@@ -659,14 +656,11 @@ impl From<String> for NmiStatus {
 
 #[derive(Debug, Deserialize)]
 pub struct SyncTransactionResponse {
-    #[serde(rename = "transaction_id")]
     transaction_id: String,
-    #[serde(rename = "condition")]
     condition: String,
 }
 
 #[derive(Debug, Deserialize)]
 struct SyncResponse {
-    #[serde(rename = "transaction")]
     transaction: SyncTransactionResponse,
 }

## Type of Change
<!-- Put an `x` in the boxes that apply -->

- [x] Bugfix

## Description
<!-- Describe your changes in detail -->
This PR aims at fixing the PSync flow for NMI connector that used to keep the payment status as Pending even after doing the PSync call. FYI, NMI requires you to do a PSync call everytime to get the payment status updated and hence this PR is the hotfix for NMI PSync flow.

## Motivation and Context
<!--
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).
-->
I fixed yet another bug! 


## How did you test it?
<!--
Did you write an integration/unit/API test to verify the code changes?
Or did you test this change manually (provide relevant screenshots)?
-->
Manually.

Payment Create Flow
<img width="1292" alt="image" src="https://github.com/juspay/hyperswitch/assets/69745008/0221bfdb-009c-4978-8cf4-6069abae992d">
<img width="1292" alt="image" src="https://github.com/juspay/hyperswitch/assets/69745008/cb11cb64-8645-4699-8c6a-0c0380df821f">

Payment Refund Flow
<img width="1292" alt="image" src="https://github.com/juspay/hyperswitch/assets/69745008/9350ae0f-fc6f-42c7-9ac2-97cd811a45e5">
<img width="1292" alt="image" src="https://github.com/juspay/hyperswitch/assets/69745008/34e74722-1688-4e22-a6b2-f477798ed395">



## Checklist
<!-- Put an `x` in the boxes that apply -->

- [x] I formatted the code `cargo +nightly fmt --all`
- [x] I addressed lints thrown by `cargo clippy`
- [x] I reviewed submitted code
