Issue:
Bug: [FEATURE]: [Tsys] Use `connector_request_reference_id` as reference to the connector



### :memo: Feature Description 

- We transmit our reference id from Hyperswitch to the connector, enabling merchants to subsequently locate the payment within the connector dashboard.
- Presently, there is a lack of uniformity in this process, as some implementations employ `payment_id` while others utilize `attempt_id`.
- This inconsistency arises from the fact that `payment_id` and `attempt_id` correspond to two distinct entities within our system.

### :hammer: Possible Implementation 

- To mitigate this confusion, we've introduced a new field called `connector_request_reference_id` in our RouterData. 
- This id should replace them as a reference id to the connector for payment request. 
- One might need to have exposure to api docs of the connector for which it is being implemented.
- You can check this PR for further reference https://github.com/juspay/hyperswitch/pull/2052

:bookmark: 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_request_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 #2319  !


## 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/6ad99801-288c-4bd5-b125-ddf19c645f1a)

- 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/6ad99801-288c-4bd5-b125-ddf19c645f1a)

- 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 d8516c8293b..83134568c05 100644
--- a/crates/router/src/connector/tsys/transformers.rs
+++ b/crates/router/src/connector/tsys/transformers.rs
@@ -34,6 +34,7 @@ pub struct TsysPaymentAuthSaleRequest {
     cardholder_authentication_method: String,
     #[serde(rename = "developerID")]
     developer_id: Secret<String>,
+    order_number: String,
 }
 
 impl TryFrom<&types::PaymentsAuthorizeRouterData> for TsysPaymentsRequest {
@@ -57,6 +58,7 @@ impl TryFrom<&types::PaymentsAuthorizeRouterData> for TsysPaymentsRequest {
                     terminal_operating_environment: "ON_MERCHANT_PREMISES_ATTENDED".to_string(),
                     cardholder_authentication_method: "NOT_AUTHENTICATED".to_string(),
                     developer_id: connector_auth.developer_id,
+                    order_number: item.connector_request_reference_id.clone(),
                 };
                 if item.request.is_auto_capture()? {
                     Ok(Self::Sale(auth_data))