Issue:
Bug: [BUG] Braintree throws payment status as succeeded while it is still processing the payment



### Bug Description

When you make a payment through Braintree, it directly gives the payment status as succeeded instead of Processing since `SubmittedForSettlement` has to be mapped to `Pending` instead of `Charged`.   
So, even the payment fails, the user will be showed as succeeded.
This effectively stops the user from making a refund as the user who looks at the payment status as `succeeded`. Instead, mapping to processing is recommended since the payment status of the payment is changed every night and the time depends on the processor.

### Expected Behavior

It should show the status as processing.

### Actual Behavior

Payment status shows succeeded.

### Steps To Reproduce

1. Make a payment through Braintree
2. Payment status will be succeeded. 

### Context For The Bug

![image](https://github.com/juspay/hyperswitch/assets/69745008/01a4d74b-1ca4-4a48-949a-60cb8ce00ebd)


### Environment

Are you using hyperswitch hosted version? Yes
`x-request-id`: `376b2049-bbff-44cf-83ba-1930a3eec311`


### 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!

Pull request description:
## Type of Change
<!-- Put an `x` in the boxes that apply -->

- [x] Bugfix

## Description
<!-- Describe your changes in detail -->
`SubmittedForSettlement` in Braintree is set to `Pending` since it `SubmittedForSettlement` changes is a nightly process and takes time to finish the payment. Docs attached below:
- https://developer.paypal.com/braintree/docs/reference/general/statuses#submitted-for-settlement
- https://developer.paypal.com/braintree/docs/reference/general/testing#settlement-status

Only if the payment is successful (Settled) or failed (Declined), a webhook is sent from Braintree's end.

## 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).
-->
This change is required as the connector returns the payment as succeeded instead of Processing / Pending. This does not allow the user to initiate a refund. Trying to do the same results in an error that states that the payment is still processing. Also, if the payment fails i.e., the payment status changes from `SubmittedForSettlement` to `Decline`, the user will still be showed as the payment in succeeded status itself and not as failure.


## 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


## 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


Testing:

Manually

Patch:
diff --git a/crates/router/src/connector/braintree/transformers.rs b/crates/router/src/connector/braintree/transformers.rs
index b5e81097ca1..ce1fa2262ad 100644
--- a/crates/router/src/connector/braintree/transformers.rs
+++ b/crates/router/src/connector/braintree/transformers.rs
@@ -184,9 +184,7 @@ pub enum BraintreePaymentStatus {
 impl From<BraintreePaymentStatus> for enums::AttemptStatus {
     fn from(item: BraintreePaymentStatus) -> Self {
         match item {
-            BraintreePaymentStatus::Succeeded
-            | BraintreePaymentStatus::SubmittedForSettlement
-            | BraintreePaymentStatus::Settling => Self::Charged,
+            BraintreePaymentStatus::Succeeded | BraintreePaymentStatus::Settling => Self::Charged,
             BraintreePaymentStatus::AuthorizedExpired => Self::AuthorizationFailed,
             BraintreePaymentStatus::Failed
             | BraintreePaymentStatus::GatewayRejected