[BUG] (connector): [Netcetera] Fix three_ds_requestor_challenge_ind field in Netcetera Response

[dgeee13]

Bug Description

Currently we are not recieving field three_ds_requestor_challenge_ind in Netcetera's authentication response since the struct is incorrectly declared in the transformers file.

1. three_ds_requestor_challenge_ind is currently a part of NetceteraAuthenticationSuccessResponse enum, but it should be a field inside authenitcation request
2. three_ds_requestor_challenge_ind has type optional string, whereas it is vector of string (ref documentation - https://3dss.netcetera.com/3dsserver/doc/2.5.2.1/3ds-authentication)

Current structure

NetceteraAuthenticationSuccessResponse{
....
three_ds_requestor_challenge_ind: Option<String>
...}

Correct structure

NetceteraAuthenticationSuccessResponse{
....
authentication_request: {
three_ds_requestor_challenge_ind: Option<Vector<String>>,
}
...}

Expected Behavior

When the struct is fixed in code, expected behavior is to recieve three_ds_requestor_challenge_ind field in Netcetera's authentication response.

correct structure

NetceteraAuthenticationSuccessResponse{
....
authentication_request: {
three_ds_requestor_challenge_ind: Option<Vector<String>>,
}
...}

Actual Behavior

Currently we are not recieving field three_ds_requestor_challenge_ind in Netcetera's authentication response since the struct is incorrect, and as a result sending challengeCode as null to Cybersource

Steps To Reproduce

Provide an unambiguous set of steps to reproduce this bug. Include code or configuration to reproduce, if relevant.

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'

Context For The Bug

No response

Environment

Are you using hyperswitch hosted version? Yes/No
If yes, please provide the value of the x-request-id response header to help us debug your issue.

If not (or if building/running locally), please provide the following details:

1. Operating System or Linux distribution:
2. Rust version (output of rustc --version): ``
3. App version (output of cargo r --features vergen -- --version): ``

Have you spent some time checking if this bug has been raised before?

• I checked and didn't find a similar issue

Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines

Are you willing to submit a PR?

Yes, I am willing to submit a PR!