Issue:
Bug: [FEATURE]: [Tsys] Use `connector_response_reference_id` as reference to merchant



### :memo: Feature Description

- Reference id are used to map transactions in the connector’s dashboard.
- Hyperswitch manages several reference ids, such as `payment_id`, `attempt_id`, and `connector_transaction_id` for a single transaction. 
- However, merchants may encounter uncertainty when determining which ID to utilize in the connector dashboard to identify the payment.

### :hammer: Possible Implementation

- When we receive a response from the connector for the payment, we deserialize it and populate the `response` field in RouterData. 
- For the `TransactionResponse` type, we must fill the `connector_response_reference_id` with a corresponding reference id for the merchant to identify the transaction. 
- One might need to have exposure to api docs of the connector for which it is being implemented to decide what to fill in connector_response_reference_id.
- You can check this PR for further reference https://github.com/juspay/hyperswitch/pull/1735

🔖 Note: All the changes needed should be contained within `hyperswitch/crates/router/src/connector/`


### :package: Have you spent some time checking if this feature request has been raised before?

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

### :package: Have you read the Contributing Guidelines?

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

###  :sparkles: Are you willing to submit a PR?


Pull request description:
## Type of Change

- [x] New feature


## Description

The `connector_response_reference_id` parameter has been set for the Tsys Payment Solutions for uniform reference and transaction tracking.


### File Changes

- [x] This PR modifies the Tsys Transformers file.

**Location- router/src/connector/tsys/transformers.rs**

## Motivation and Context

This PR was raised so that it Fixes #2350 !


## How did you test it?

- **I ran the following command, and all the errors were addressed properly, and the build was successful.**

```bash
cargo clippy --all-features
```

![build](https://github.com/juspay/hyperswitch/assets/47860497/39d95c9a-d14b-44c5-a402-9bd9cecf8b8e)

- The code changes were formatted with the following command to fix styling issues.

```bash
cargo +nightly fmt
```

## 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 the submitted code


Testing:
- **I ran the following command, and all the errors were addressed properly, and the build was successful.**

```bash
cargo clippy --all-features
```

![build](https://github.com/juspay/hyperswitch/assets/47860497/39d95c9a-d14b-44c5-a402-9bd9cecf8b8e)

- The code changes were formatted with the following command to fix styling issues.

```bash
cargo +nightly fmt
```

Patch:
diff --git a/crates/router/src/connector/tsys/transformers.rs b/crates/router/src/connector/tsys/transformers.rs
index 5aa4574c91e..d8516c8293b 100644
--- a/crates/router/src/connector/tsys/transformers.rs
+++ b/crates/router/src/connector/tsys/transformers.rs
@@ -192,12 +192,14 @@ fn get_error_response(
 
 fn get_payments_response(connector_response: TsysResponse) -> types::PaymentsResponseData {
     types::PaymentsResponseData::TransactionResponse {
-        resource_id: types::ResponseId::ConnectorTransactionId(connector_response.transaction_id),
+        resource_id: types::ResponseId::ConnectorTransactionId(
+            connector_response.transaction_id.clone(),
+        ),
         redirection_data: None,
         mandate_reference: None,
         connector_metadata: None,
         network_txn_id: None,
-        connector_response_reference_id: None,
+        connector_response_reference_id: Some(connector_response.transaction_id),
     }
 }
 
@@ -215,7 +217,12 @@ fn get_payments_sync_response(
         mandate_reference: None,
         connector_metadata: None,
         network_txn_id: None,
-        connector_response_reference_id: None,
+        connector_response_reference_id: Some(
+            connector_response
+                .transaction_details
+                .transaction_id
+                .clone(),
+        ),
     }
 }