Issue:
feat(core): external authentication related schema changes for existing tables

## Type of Change
<!-- Put an `x` in the boxes that apply -->

- [ ] Bugfix
- [x] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD

## Description
<!-- Describe your changes in detail -->
Made schema changes to payment_attempt, payment_intent  and merchant_account tables in order to accommodate core implementation of separate authentication feature. 

Hyperswitch currently uses the "Processor driven approach" for 3DS and is now looking to move towards "Third Party 3DS provider approach" - Using a specialized 3DS provider for checking card enrollment and 3DS authentication
Eg: Cardinal, Netcetra

The 3DS authentication can be done once and the authentication response that we get can be sent to any processor to authorize the payment.

Columns added:
BusinessProfile:
 1. authentication_connector_details: default null

PaymentAttempt:
1. external_three_ds_authentication_attempted: default false
2. authentication_connector: default null
3. authentication_id: default null

PaymentIntent:
1. request_external_three_ds_authentication: default null 


### Additional Changes

- [ ] This PR modifies the API contract
- [x] 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`
5. `crates/router/src/configs`
6. `loadtest/config`
-->


## 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 it is an obvious bug or documentation fix
that will have little conversation).
-->
Separate authentication feature


## 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)?
-->
Compiler guided and Sanity testing to make sure it's backward compatible
This feature can only be tested once core changes are done.

## 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
- [ ] I added unit tests for my changes where possible
- [ ] I added a [CHANGELOG](/CHANGELOG.md) entry if applicable


Resolution:
<think>
PR Context:
- Title: fix(payouts): saved payment methods list for bank details
- Merged: 2024-02-07T09:35:00Z
- Files changed: 2 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
- [ ] Documentation
- [ ] CI/CD

## Description
Issue [#3904](https://github.com/juspay/hyperswitch-cloud/issues/3904)


### Additional Changes

- [ ] This PR modifies the API contract
- [ ] This PR modifies the database schema
- [ ] This PR modifies application configuration/environment variables

<!--
Provide links to t
</think>

To implement this, you'll need to modify:


**Detailed Implementation:**


**Commit 1:** fix(payouts): saved payment methods list for bank details (#3507)
Co-authored-by: Kashif <mohammed.k
Files to modify:


**crates/router/src/core/payment_methods/cards.rs**
  Modify existing code

**crates/router/src/core/payment_methods/transformers.rs**
  Modify existing code