fix(connector): [BOA/CYBERSOURCE] Update error handling

[deepanshu-iiitu]

Type of Change

• Bugfix
• New feature
• Enhancement
• Refactoring
• Dependency updates
• Documentation
• CI/CD

Description

HOTFIX PR:
The field reason in struct BankOfAmericaErrorResponse/ ErrorResponse(in cybersource) will be handled as a string instead of handling it as an enum. The reason for this is the absence of proper documentation for error reason at the connector's end.

Authentication error will also be handled properly now.

Additional Changes

• This PR modifies the API contract
• This PR modifies the database schema
• This PR modifies application configuration/environment variables

Motivation and Context

Original PR: #3156

How did you test it?

1. Try to create a payment by passing billing.last_name as an empty string. You should be then able to successfully generate an error.

curl --location 'http://localhost:8080/payments' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header 'api-key: API_KEY_HERE' \
--data-raw '{
  "amount": 100,
  "currency": "USD",
  "confirm": true,
  "capture_method": "automatic",
  "email": "[email protected]",
  "name": "John Doe",
  "authentication_type": "no_three_ds",
  "return_url": "https://google.com",
  "payment_method": "card",
  "payment_method_type": "credit",
  "payment_method_data": {
    "card": {
      "card_number": "4111111111111111",
      "card_exp_month": "12",
      "card_exp_year": "30",
      "card_holder_name": "joseph Doe",
      "card_cvc": "123"
    }
  },
  "billing": {
    "address": {
      "line1": "1467",
      "city": "San Fransico",
      "state": "Dubai",
      "zip": "94122",
      "country": "AE",
      "first_name": "joseph",
      "last_name": ""
    }
  }
}'

Response:

2. To generate an authentication error response just put wrong api keys and try to do a payment. You should get the following error in that case:
   

Checklist

• I formatted the code cargo +nightly fmt --all
• I addressed lints thrown by cargo clippy
• I reviewed the submitted code
• I added unit tests for my changes where possible
• I added a CHANGELOG entry if applicable